Capture form name on open

[bcarvinm]

I don't know if this is even possible, but I want to capture in a table
the name of every form along with the date when it is opened. I'm
hoping i can put this in a module so I don't have to modify every forms
on open procedure. I'm planning on doing a redesign of my database but
I don't have the time to remove a form and see if anyone complains. I
figure this would be the fastest way to figure out what people are
actually using rather than what they think they are using. I'm using
Access 97 if that makes a difference.

Thanks for any help.

Brian

 

[Rick Brandt]

I don't know if this is even possible, but I want to capture in a
table the name of every form along with the date when it is opened.
I'm hoping i can put this in a module so I don't have to modify every
forms on open procedure. I'm planning on doing a redesign of my
database but I don't have the time to remove a form and see if anyone
complains. I figure this would be the fastest way to figure out what
people are actually using rather than what they think they are using.
I'm using Access 97 if that makes a difference.

Thanks for any help.

Brian

No way that I know of that wouldn't require you to put something in the Open or
Load event of every form. That something *could* be a generic function call
though that need not be different per form.

 

['69 Camaro]

Hi, Brian.

I'm
hoping i can put this in a module so I don't have to modify every forms
on open procedure.

Access uses an event-driven architecture, so unless you have a switchboard form
that opens all other forms, you will need to put VBA code in either the
OnOpen( ) event or OnLoad( ) event of each form. If you have the switchboard,
you'll need to insert code in its module wherever any form is opened, so that
would be a lot of work also.

I'm planning on doing a redesign of my database but
I don't have the time to remove a form and see if anyone complains. I
figure this would be the fastest way to figure out what people are
actually using rather than what they think they are using.

If this were a professional software application, the next phase of the software
development lifecycle would be to interview the users and managers to get
information for the new (or revised) requirements document. If your application
is complex and you rely on an automated recording of what's being used, you may
find some of the forms were opened by mistake ("Oops. Not that one."), and
you'll waste time redesigning those forms for the next version.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.

 

[bcarvinm]

I was afraid that was the answer. The biggest problem with the
database is that it hasn't had a dedicated DBA in about 5 years and
whenever someone wanted a form or a table added they just did it and
now I'm trying to fix the mess before it breaks completely.

I was certainly planning on talking with the users/managers for the
requirement doc, but I wanted to have some sort of record of what
people actually used, rather than what they thought they used, just as
a starting place.

Thanks to both you and Rick for the help.

Brian

 

['69 Camaro]

You're welcome, Brian. Good luck with it.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.