[AccessD] events question

Oops - I should have written, ". . . in a standard Module."

It sounded like you do this frequently on many of your forms - if that's
correct then writing your own utility code would work well.  But if it's
something you do infrequently, then the 'manual' method is probably better.

For example, I have a procedure which sets a number of parameters for all my
forms that I run before they are released.  And another for reports.  And
another for tables to set Subtable = [None], for better performance.  

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
Sent: Friday, December 07, 2007 10:24 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] events question

>
> Create a global function called GlobalMouseOver in a standard procedure.
>
> Now, create some looping code for yourself which writes GlobalMouseOver()
> into all the appropriate Mousing events in the appropriate controls.

========I don't think I know how to do that. But, it sounds like just as 
much work as the actual calls, so I'm not sure there's a benefit unless you 
had a whole lot of controls -- would you agree?

Susan H. 

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com