## JETCOMP.EXE arguments

I want to compact an access MDB database file using JetComp.exe . I want to pass the name of the file ( and the destination file) to Jetcomp.exe . However, JetComp.exe does not seem to respond. I tried the following:

jetcomp.exe -src:{"G:\my database.mdb"} -dst:"G:\my compacted database.mdb"


I can't use the GUI version of Jetcomp.exe as I want to include the line above in a database upgrader.

All the best, Seb

Use the DBEngine.CompactDatabase method instead of JetComp. One less thing to distribute.

I also go a bit further. See Backup, do you trust the users or system administrators?

Compacting a Jet Database from the command line using JetComp , Microsoft provides a utility which can be used to compact Jet databases from the command line. This utility can sometimes repair and compact� JETCOMP.EXE arguments. Ask Question Asked 9 years, 6 months ago. Active 3 months ago. Viewed 2k times 1. I want to compact an access MDB database file using JetComp

Although the question is quite old, I'd like to post an answer since using JetComp may still be of use for someone.

However, JetComp.exe does not seem to respond.

Because you used the wrong syntax. This is how it works:

jetcomp.exe -src:"G:\my database.mdb" -dest:"G:\my compacted database.mdb"


Microsoft Access JETCOMP.exe - TechNet Articles, Next, under 'Additional Compact Options' tab, select the appropriate options. Click Compact. Limitations of JETCOMP.exe. While the Jet Compact� What is JETCOMP.exe? It is a freeware, standalone utility that allows to compact Access databases created with Microsoft Jet database engine 3.x and 4.x. Also, JETCOMP.exe may help you recover corrupt databases when run in conjunction with the Jet database engines 3.x and 4.x.

ssc is correct. JetComp works! If the database is password protected use this syntax

jetcomp.exe -src:"G:\mydatabase.mdb" -wPASSWORD -dest:"G:\mycompacteddatabase.mdb"


[PDF] JetComp.exe Readme File, Under Additional Compact Options, set the appropriate options. 5. Click Compact . Errors Encountered in Earlier Versions of the Microsoft Jet Database Engine. In � Using JETCOMP.exe for corrupted database When I try to open my Creative Media Source software (provides access to my MP3 music files) I get a message saying I have a corrupted database and to run Jet Engine 4.0.

Jetcomp.exe Command-Line switches, With Jetcomp.exe (vers 4), I used the "-?" (no quotes). It displayed a window showing all possible switches/params. But it doesn't show any� I want to automate running JETCOMP.exe utility to compact an Access database with vbscript using the .run command however I first need to get the utility to run before I can automate it. I don't know if I should run it with CMD /C or without at the DOS prompt because neither seems to work. I

JETCOMP.exe utility switch to path to database to compact, p:\ath\to\jetcomp.exe /? to see the command line options. Experiment with creating the proper command line to run jetcomp to compact your database, and when� p:\ath\to\jetcomp.exe /? to see the command line options. Experiment with creating the proper command line to run jetcomp to compact your database, and when you have it, use the Run method in your vbscript code to execute it.

JetComp 4.0 command line options, Are there any command line switches to start JetComp 4.0? I want to schedule a task to run it nightly unattended. TIA! The Jet compact utility, jetcomp.exe, is a stand-alone utility that compacts databases created with Microsoft Jet database engine 3.x and 4.x. This utility may be run in conjunction with Microsoft Jet database engine 3.x and 4.x for recovering corrupted databases. Although you can run the Microsoft Access Compact utility or the CompactDatabase method with Microsoft Jet database engine 3.x and 4.x, Jetcomp .exe may be able to recover some databases that these utilities cannot.

##### Comments
• Tony Toews - Thanks for the reply. Do you think I should use the method described in this article ? ( codeproject.com/KB/database/mdbcompact_latebind.aspx )
• I'm not familiar with JRO but it should work the same way when it comes to compacting.
• JRO may or may not be installed on the PC you're working with, but DAO definitely will be. JRO has no reason to exist except for the stupidity of MS's ADO-everywhere campaign c. 2000, when they tried to replace Jet's native interface, DAO, with a non-native abstraction layer, ADO. JRO should be ignored for every purpose, except the one thing it does that can't be done with DAO, and that's initiate an indirect synch between two replicas in a replicated Jet database.