>>Anybody have a routine to determine if the forms in a project are actually called?
>>
>>Thanks
>
>In my system, forms are mostly called indirectly, not through a menu option. I.e., the user sees the form in a list (loaded from a table, options seen by user vary depending on user level and department).
>
>The problem (in my case) is to determine whether someone actually ever uses the form, or not - that is, some forms may have been created, but never used, even though they are accesible. To have this statistics, I created a usage log, i.e., every time a user opens a form, a record is written to table FormUsage (contents: login, form name, datetime).

I was thinking of the same approach, but then remembered that some things are used annually (e.g. inventories) and some only when the new boss demands them :). It is a maintenance nightmare, though, because they start using something that nobody touched in months, and in case of any bugs it's then hard to remember how exactly it was supposed to work.

And if we removed any forms which weren't touched for a while... well, maybe some of them were supposed to handle situations which just didn't happen, or are a feature that the users didn't begin to use yet, but they might. So while it's good for statistical purposes, it's not a sure fire way to see what is used and what not, it may create a lot of false negatives.

OTOH, scanning all the files in the project for form calls may discover a whole range of forms which are called from other forms, while their caller forms are not in use at all. I.e. there could be a lot of false positives that way.