Accessing Protected Databases in "Development" Mode

[Mihalis]

Hello,

I have a very simple question, but that's giving me a lot of trouble :

If I have a unprotected access database with a startup form, but I want to
enter in "development" mode, I just need to press the SHIFT key while opening
the database...but if the same database is protected, using a workgroup
created in a .mdw file, how can I do the same thing, i.e., enter in
"development" mode?

Thanks,
Best Regards,
Mihalis

 

[Douglas J Steele]

As long as the AllowBypassKey hasn't been disabled, you should be able to
still get into development mode.

Whether or not you can do anything will depend on what rights you have in
the database.

 

[Lynn Trapp]

After you enter the username and password, hold the shift key down and allow
the database to open. It should bypass the startup options.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm
Jeff Conrad's Access Junkie List:
http://home.bendbroadband.com/conradsystems/accessjunkie.html

 

[Larry Linson]

If I have a unprotected access database
with a startup form, but I want to enter
in "development" mode, I just need to
press the SHIFT key while opening
the database...but if the same database is
protected, using a workgroup created in
a .mdw file, how can I do the same thing,
i.e., enter in "development" mode?

It is possible to "protect" a database so well that it is very difficult to
get into it in "development" mode. If you intend to protect it that well,
you should save a less-well-protected database for development use, then
fully-protect a copy of that when you have changed it and want to distribute
to your users.

In any case, you should split the database into a Front-End (the application
itself, with queries, forms, reports, macros, modules, and perhaps local
lookup tables) and Back-End (tables, relationships, and data). Most of us
find that, once a database has gone into production, we have to change the
Front-End features far more often than we have to change the Back-End or
both.

Larry Linson
Microsoft Access MVP