After Compact event???

gblack

Registered User.
Local time
Today, 20:13
Joined
Sep 18, 2002
Messages
632
I have inherited an Access Database, which programmatically establishes linked tables when the front end of the (split) database is opened. The process is kicked off by a startup form then after the table links are established... opens a switchboard.

The issue that I am having is that they now would like me to make this thing work on a very restricted network environment that doesn't allow "trusted connections" nor "macros enabled", by default. Thusly, every time one opens the database, they are haulted and must choose "enable macros" by hand, which stops the open form event and haults the linking process.

Once you choose "enable macros" the database then compacts (is this standard after enable macros is chosen?).

Anway... I was wondering two things: First and foremost, is there such a thing as an after compact event, or any way to kick off code using compact as the triggering mechanism? Secondly, has anyone dealt with such harsh restrictions in their code, in any way, and might have some hints to make my life easier?

Regards,
Gary
 
Ok scratch that last question...

Let me ask this in a different way...

My issue is that when I choose to enable Macros manually (vs. the nomral process of using a startup form), something happens.. but I don't know where the code is kicking off. So when I go in and try to debug, seemingly none of my stops actually stop the code... yet some code is running.

So, I am just wondering what actually fires off when you choose to manually "enable macros" after your initial database open gets haulted/stalled by security measures?... does anyone know what takes place and has the time to explain?

Regards,
Gary
 
Re: Ok scratch that last question...

My issue is that when I choose to enable Macros manually (vs. the nomral process of using a startup form), something happens.. but I don't know where the code is kicking off. So when I go in and try to debug, seemingly none of my stops actually stop the code... yet some code is running.
What do you think runs when the macros are enabled? The only code I would imagine runs is in your startup form or an AutoExec macro.
 
When you click ENABLE MACROS in Access 2007 or above it just restarts the database but allowing the restricted stuff to run. It doesn't compact it, it just starts it over.
 
When you click ENABLE MACROS in Access 2007 or above it just restarts the database but allowing the restricted stuff to run. It doesn't compact it, it just starts it over.
Ah, perhaps that's what makes gblack think that it's being compacted.
 

Users who are viewing this thread

Back
Top Bottom