user-hostile
Registered User.
- Local time
- Today, 15:47
- Joined
- Oct 20, 2007
- Messages
- 10
Hey; I was troubleshooting a database app that I use to perform update/maintenance on other databases. My VBA code does things like modify tables, compact/repair, ShiftKeyBypass, etc. to other "external" databases the user specifies (you input the path name, and the db does the action on the database specified).
Anyway, I noticed the other day the code was bombing (error 3033; no permissions) when using the DAO.OpenDatabase command. Out of habit, I often open databases with the shift key held down to disable the default form, autoexec macro, etc., from executing, and I had done this for this database. So out of curiosity I opened my admin database without using the shift key, and voila, NO 3033 error! I then reopened it with the shift key and...YES: 3033 error! Hmm. A reproducible error.
It appeared to me that holding down the shift key not only bypassed opening the startup form you specify in Tools | Startup and any Autoexec macro, but also other thing(s), such as disabling certain DAO functions. Holding the shift key clearly disallowed my VBA DAO.OpenDatabase code from working. I searched MSDN, but couldn't find a definitive answer. Does someone know what EXACTLY gets disabled when you start up with the shift key? Thanks.
UH
Anyway, I noticed the other day the code was bombing (error 3033; no permissions) when using the DAO.OpenDatabase command. Out of habit, I often open databases with the shift key held down to disable the default form, autoexec macro, etc., from executing, and I had done this for this database. So out of curiosity I opened my admin database without using the shift key, and voila, NO 3033 error! I then reopened it with the shift key and...YES: 3033 error! Hmm. A reproducible error.
It appeared to me that holding down the shift key not only bypassed opening the startup form you specify in Tools | Startup and any Autoexec macro, but also other thing(s), such as disabling certain DAO functions. Holding the shift key clearly disallowed my VBA DAO.OpenDatabase code from working. I searched MSDN, but couldn't find a definitive answer. Does someone know what EXACTLY gets disabled when you start up with the shift key? Thanks.
UH