Bob Heygood
bheygood at abestsystems.com
Sat Feb 15 18:34:00 CST 2003
Sometimes for reasons including John's renaming suggestion, the "event procedure" choice is not selected in the property sheet for the control. So, even though you may have a control and code they may not be connected. Good luck, Bob Heygood accesspro at nospamcox.net -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com]On Behalf Of John W. Colby Sent: Friday, February 14, 2003 3:52 PM To: accessd at databaseadvisors.com Subject: RE: [AccessD] Event driven programming? Hmmm... the only time I've seen this is when I renamed the control. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: accessd-admin at databaseadvisors.com [mailto:accessd-admin at databaseadvisors.com]On Behalf Of Keith Kovala Sent: Friday, February 14, 2003 6:35 PM To: AccessD at databaseadvisors.com Subject: [AccessD] Event driven programming? Here's a fun one. You write a nice little routine to fire on an event like Change, Keypress, or whatever. Test it and it works as expected. Then, for whatever reason, suddenly that "event" you were triggering on quits firing, even though it should be. For example, a keyup event on a textbox, pressing keys to your heart's content the event never fires. Place a msgbox in the event, place a breakpoint there, nothing.... Just never performs any actions. What gives? I've tried decompiling the app, and a compact and repair, but still no joy. This is in A2K, on Win2K. Thanks for any ideas, Keith L. Kovala _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com