Jetcomp.exe

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Does anyone know if Jetcomp.exe can be run asynchrosously? I have written a
wrapper application for my clients to easily Backup and or Compact thier
databases themselves (They're Non Techies) using a very user-friendly GUI.
However I need to "Shell" out to Jetcomp.exe and still be able to "DoEvents"
so to speak. Jetcomp doesn't "return" control to my VBA code until after it
is finished compacting.

Thanks in advance for any help you can provide.
 
Seehttp://www.mvps.org/access/api/api0004.htmat "The Access Web" for how
to wait until a shelled process has completed.

I just glanced the code but doesn't it make the shelled process
*synchronous*?
However, I've never needed to shell to Jetcomp.exe: I always use the
CompactDatabase method of the DBEngine object.

Again, isn't that *synchronous*?

FWIW I don't think there is an obvious ADO solution. Although ADO
supports asynchronous connection, fetching and execution, Jet
Replication Objects (JRO) has no events :(

Jamie.

--
 
Jamie Collins said:
I just glanced the code but doesn't it make the shelled process
*synchronous*?


Again, isn't that *synchronous*?

FWIW I don't think there is an obvious ADO solution. Although ADO
supports asynchronous connection, fetching and execution, Jet
Replication Objects (JRO) has no events :(

You're correct. I misread his requirements.

I don't believe there's any solution either.
 
You're correct. I misread his requirements.

OK, thanks for confirming.
FWIW I don't think there is an obvious ADO solution. Although ADO
supports asynchronous connection, fetching and execution, Jet
Replication Objects (JRO) has no events :(

Another thought: the JRO.JetEngine.CompactDatabase method creates a
new file, rather than overwriting the old one. So if you could kick
off the process while continuing execution (e.g. start a new thread
e.g. JRO code in a DLL, shell out, Windows timer, etc) you could poll
the file system to detect when the file has been created, remembering
to build in a guaranteed end point e.g. write a dummy mdb if the
compact fails and timeout the whole process after several minutes.
Yes, all the above is intentionally vague <g>.

Jamie.

--
 
Back
Top