Drew Wutka
DWUTKA at marlow.com
Fri May 2 18:30:54 CDT 2003
I didn't write the original post, but it said the issue was opening an instance of Access, with VB/VBA, and then opening a database, without the startup running. As far as I know, there are only two ways to do this. One method is to disable the startup from with the database itself. ie, have it look for a specific flag in a record, or have it check for a specific command line argument, so that when it starts, the startup code checks that 'trigger', and then stops...effectively 'bypassing' the startup stuff. The other method is to actually open the database and use a 'sendkeys' approach to have the shift key held when the code opens the database. Drew -----Original Message----- From: Susan Harkins [mailto:harkins at iglou.com] Sent: Friday, May 02, 2003 6:21 PM To: accessd at databaseadvisors.com Subject: Re: [AccessD] Access VB question I know, but without giving it too much thought, I thought it might be a place to start -- don't really know what the real problem is. Susan H. Yes, but that only sets whether the shift key bypasses the startup or not. It doesn't actually trigger it. Drew -----Original Message----- From: Susan Harkins [mailto:harkins at iglou.com] Sent: Friday, May 02, 2003 5:27 PM To: accessd at databaseadvisors.com <mailto:accessd at databaseadvisors.com> Subject: Re: [AccessD] Access VB question If you could someone set the Access database setting the AllowBypassKey property before you try to open it in VB? Do you have to disable it from inside VB? Susan H. I may be mistaken, but nothing in that code bypasses the startup stuff. Drew Does anyone know how to programmatically open an access database in VB, bypassing the startup options? _____ _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030502/9a7773db/attachment-0001.html>