Discussion Locked

Keeping track of program usage

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This week's Visual Basic e-newsletter demonstrates how you can implement a technique for keeping track of program usage.

Do you think that it would be useful to keep track of program usage? If you already do, are you using a different technique other than the one the author describes? Please let us know.

If you aren't subscribed to our free Visual Basic e-newsletter, click the following link to automatically sign up:
http://nl.com.com/MiniFormHandler?brand=builder&subs_channel=bldr_front_door&list_id=e065&tag=fb

4 replies

by gnc

As I've been out of direct programming awhile, could you please explain if/how these types of techniques have an effect on the registry size and does an increaed registry size effect performance. Thank you.

by peter

The registry is a rather large file, hundreds of kbytes at least. The few dozen bytes that this technique will add would not have any noticable effect on performance.

by bucky kaufman (mcsd)

re:
Do you think that it would be useful to keep track of program usage?
----- ----- ----- ----- ----- -----

That, of course, depends on the enviornment - and the cost-benefit ratio. In a small office, it's probably not important if a user runs 1-2-3 more often than VisiCalc.

In a large office, it could indicate that the users are not using the updated VisiCalc based application.

Then there's the whole CBA thing. If it costs $2500 to build an app to monitor usage - but you don't have a business need for it - what have you gained?

by vcr

I prefer to create a file to store any information concerning an application. This has the advantage of being easily removed when the app is uninstalled.

This discussion is closed to new replies.