DS said:
Wow, Thank you for all of the info! Its much appreciated.
You're welcome.
What are the pitfalls of hiding the Access environment?
Here are some disadvantages that I found with this technique:
1. Your code better be rock solid with error handling!
(sound advice anyway) Otherwise, a crash could result
from an unhandled error.
2. Previewing reports on the screen presents additional
problems because all your forms are Pop Up. Sandra Daigle
provided me with some code to get around this, but it's
still a pain and does not work across all Access versions.
With Pop-up forms, any reports appear behind the form.
Toggling visibility is a nightmare and does not always work
with this code.
3. You can't use custom menu and toolbars. Big
disappointment there!
4. I thought I remember some issues with minimizing the
windows. I could be wrong so don't quote me on that.
5. Nothing appears in the Taskbar so not-so-technical users
may shut down Windows without realizing the program is
still running. Corruption could result.
The ONLY time I found a great use for this code was to
create a single form MDE file that was used as a Login
form to my main secured databases. With a secured database
you are presented with the generic Access login screen.
Pretty poor looking in my opinion. So I created a form in
this other unsecured MDE file that hides the application
window. All it does is present a few options to the user
for logging into the regular database, the sample
database, or backup the data files. The user enters their
User Name/Password and that information is passed in code
to open the secured databases. Works great, looks great,
but I really would not want to use this code anywhere
else. Too many limitations. You're better off customizing the
application with custom tool bars and menu bars. Windows
users are used to these anyway so why fight it? Just my 2 cents.