is there a way of running the auto exec macro as code not a macro

i want to create a Access 97 MDE File, and would like the Autoexec macro
replaced with a module function so as not to expose the events of the
autoexec to the user!

also...

i'd like to stop the user from adding any new objects to  the MDE File (i.e.
Tables, Queries, Macros)

is there a WithEvents or similar to check and prevent when a new object is
added to an Access database??

Thanks

Jado

Then add the code to a form which you set up to be opened when the
database is opened. This is also somewhere in the menus of Access 97,
although MS likes to move things around and I forget where it was in
that version of Access.

The steps will then be:
    - user opens database
    - database opens form specified by designer
    - form's OnOpen event calls code

HTH,
--

    National Library of Canada
 -- Nothing in the above should be construed to represent
    anything other than my own opinions and personal reality. --

i thought that might be the only way to do this...

so i've done all that, but for some reason my Startup Form wont hide when i
use the command

Me.Visible = False

Any Ideas??

Thanks

Jado

Otherwise, I tested the Me.Visible = False in the Open, Load and Current
Event and it worked every time.

--
HTH
Van T. Dinh
MVP (Access)

Weird!

i've created a new unbound form.  i haven't changed any default settings
form the form.  in the OnLoad Event i have this...

Me.Visible = False
msgbox "Do Autoexec Stuff"

i have changed some options on the Startup Properties screen but thats it!

i'll try it in another untouched db to see if that the problem!

if you've any other ideas, please post!

Thanks

Jado

Well...

when you said it worked for you, how were you activating the form??

if i open my form in design view, then click the view form button on the
form view bar, the code seems to work fine!!

but if i save my form, close it , then open it by double clicking ing the
database window...i get my message box, then the form opens in full view???

same thing if i start my form from the startup properties screen!!
is this normal??

could you test these and let me know if you get the same!

Thanks

Jado

--
HTH
Van T. Dinh
MVP (Access)

True.  It won't work this way.

You need to use the AutoExec macro (tested in A2K) with the macro action to
open the Form in "Hidden" mode rather than the StartUp Form in the Options
...

looks like i'll need to use the Autoexec macro after all..

so just to clarify...

you don't know of a code equivilent for the Autoexec macro...

i was hoping there would be something like:-

WithEvents Application.Initialize
' Do Autoexec Stuff
'---------------------------

i think i'll be able to achieve results even with the macro as long as i use

AllowBypassKey = False to disable opening the DB whilst holding ShiftKey
and hide the DB Window and built-in Meny Bars

Thanks

Jado

--
Dirk Goldgar, MS Access MVP
www.datagnostics.com

(please reply to the newsgroup)

(provided that you don't need to keep the Form open & hidden)

Thanks
Van T. Dinh
MVP (Access)

Are you aware that you only have to disable the AllowBypassKey ONCE and it
will stay disabled until you enable it again?

--
HTH
Van T. Dinh
MVP (Access)

Thats just what i was after!

Jado

the only reason i needed the form was to run code to replace the autoexec
macro!

Thanks for all the help !
    we managed to find a solution after all!! :)
i'll keep you posted if there's any hidden problems.

have a good weekend!
Jado

Looks like this may cause a problem after all!!

if i set  Cancel  = True

this is what happens....

code in startup form now runs ok, and form is hidden or closed (whatever
"Cancel = True" does!).  The last thing the code in this form does is to
open a user input form to start using the db.  All ok so far....

The user input form has a exit db routine in it's OnUnload Event...

When i close the form to activate this Event....Nothing happens!!  The form
closes but the Event doesn't run??

Any Idea's ??

"This topic is now just out of interest as i have found an alternative
workaround!"

it would still be nice to follow it thought as it may result in a cleaner
solution to my workaround!

my workaround is to use 2 startup forms.  The first simply opens the second
in a hidden state then closes it's self.  The second form runs all the
autoexec stuff!

Thanks

Jado