Re: JETCOMP.exe utility switch to path to database to compact

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


"JRough" <jlrough@xxxxxxxxx> wrote in message
news:7da25723-d9ff-4bb1-843b-28fec2211357@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On May 16, 5:26 pm, "Al Dunbar" <aland...@xxxxxxxxxxx> wrote:
"JRough" <jlro...@xxxxxxxxx> wrote in message

news:4efc7bf9-f1af-423b-aa7b-c9424456ef60@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On May 14, 8:11 pm, JRough <jlro...@xxxxxxxxx> wrote:



On May 13, 9:07 pm, "Al Dunbar" <aland...@xxxxxxxxxxx> wrote:

"JRough" <jlro...@xxxxxxxxx> wrote in message

news:baa75d5d-2324-413d-84ab-0ccd8b94ea26@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On May 12, 9:37 pm, "Al Dunbar" <aland...@xxxxxxxxxxx> wrote:

"Janis" <Ja...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message

news:8CE13510-E01A-4BAD-B10E-5B6808118214@xxxxxxxxxxxxxxxx

I just noticed your name is Al so I guess the command is
cmd /c "c:\Program Files\Microsoft Office\JETCOMP.exe" /s
"c:\SwimClub\acsc_be"

and does that work for you?

/Al

I run this cmd /c "c:\Program Files\Microsoft Office\JETCOMP.exe" /s
"c:\SwimClub\acsc_be"

=================

I'll take that as a "yes, this works".

/Al

Al, I'm sorry it doesn't work. I don't know what happened to the
full message. I ran the command line script many times. I get an
error message something about can't find the internal program. The
DOS window scrolls too fast to read it very well. But you get the
gist. I also went back to the Jetcomp.exe utility. When you run it
manually you have to give the path to the database and the name of the
database you want to compact to and when you close it, it is not saved
so it has to be in the command line script. I think what is missing
in the command you gave me is the name to output the compacted file
to. Where would I add that to this script so I can try it again?

thanks and sorry about that, JR

I'm only doing run from the command line to run the utility. I gave
that to you exactly. Can't you run that command line script from the
command line by hitting "enter"? It does run in the DOS window. I
figure it should work first before I automate it in VBScript for the
customer. Are you saying I have to put that compacted output filename
path to the db in VBscript?

===============

When I enter that command exactly as shown, the following error message
appears:

'c:\Program' is not recognized as an internal or external command,
operable program or batch file.

I assumed from this that CMD required some sort of adjustment to the
double
quoting because of the whitespace in the path. I tried a similar command
using a copy of notepad located in a path having blanks and there was no
problem. Then I noticed that the office folder did not contain an
executable
named jetcomp.exe. I deleted my test copy of notepad.exe, and the command
that had previously worked now failed because the executable no longer
existed. But the error essage was:

'C:\Documents' is not recognized as an internal or external command,
operable program or batch file.

whereas one would normally assume that it should give the full name of the
actual file that was missing. That is indeed the behaviour when the
command
is issued without the "CMD /C".

I conclude from this that even though CMD is capable of interpreting the
pathname provided, the error reporting routine used in that context is not
able to do so. I also conclude that your computer may be missing the
jetcomp.exe file, or that you have its path incorrect.

I'd suggest you see if the command works without the "CMD /C". If so, I'm
stumped; if not, what is the error message?

Why are you using CMD /C? If you eventually get your script to work, you
will be using the .run method, so the only benefit of using CMD would be
to
redirect the output with ">". Regardless, the simplest solution might be
to
write the command you want to execute into a batch file and run that from
your script.

/Al

Sorry,
I do have JetCOmp.exe. I installed it in here so I could remember
where I put it: C:\Program Files\Microsoft Office

===================

No need to apologize. But you could perhaps have done what I suggested you
do, namely:

"I'd suggest you see if the command works without the "CMD /C". If so,
I'm stumped; if not, what is the error message?"

In addition to that, if you could provide the exact text of the error
message you get when using CMD /C, that would be helpful as well.

Until I have that info, anything else I might say could only be a guess.

/Al


.

Relevant Pages