Right-click the database window and select Startup. Click the Advanced button in the startup dialog. Uncheck "Use Access Special Keys." The changed option takes affect next time the file MDB is opened. If you want to get the best answer for your question read faq183-874 and thread183-468158. Terry L. Broadbent - DBA
SQL Server Page:
Thanks, I'll check out the article. But what I've found is that if you:
1. Open Access
2. (Without a db open) - press Alt-F11 (VBEditor opens)
3. Go back to Access Screen
4. Choose File-Open and open a .mdb and pres Alt-F11
5. And theres the code!
.mde's are different, but I still need to have access to update programatic issues, so new code needs to be generated under .mdb - hence the quandry.
I've run into this problem as well before - I'll note here that one solution to this issue is to right click the project's main title in the project browser window in the coding window. From there you can choose Properties of the project itself. VBA will then give you a screen that has two tabs, one of which is called "protection"
You can put a password on your code to lock others out, yet it will remain uncompiled (unlike making an mde file) so that you can still get in and update the code from time to time.
Ah say, there's somethin' a little "eeeeeeee" 'bout a boy who don't like basbawl...
well - it doesn't. This is just for locking things up in a jiffy. As far as I can tell, this just puts a blanket password on the whole thing that you as the developer set.
If you want something more elaborate, then you have to invest some time and coding skills, it seems.
Ah say, there's somethin' a little "eeeeeeee" 'bout a boy who don't like basbawl...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.