/repair from a .bat file - access 97

[ritenah]

I am running this command from a .bat file.

"C:\pathToAccess\MSACCESS.EXE" "C:\pathToDatabase\db.mdb" /REPAIR

Database repairs as expected, then shows the messge:

"Successfully repaired the ..." and you have to click "Ok" to get rid
of the message so that the database can close.

How does one suppress this message, so that the database shuts down
automatically?

I thought this switch was supposed to repair, then shutdown the
database without user intervention.

Any help is greatly appreciated! Thanks in advance!

[ritenah]

Somewhat interestingly and funny, is that all the searching that I've
done about this specific question always amounted to the same scenario.

There was never an answer. People more commonly replied with a "why do
you want to do that anyway", which is hilarious.

If it is impossible to SUPRESS the informative pop-up message after
running a command-line "/repair" switch with Access 97, why not just
state that?

Even more funny is that "/repair" from the cli is described by
Microsoft as a command that is supposed to automatically close access
after completion.

I don't care about the philosophical war between "/repair" and
"/compact", or the historical developments of said commands.

I simply want to know if there is a way to FORCE the /repair switch to
function as the documentation states it should.

That's all. Thanks!

ri*****@gmail.com wrote:

I am running this command from a .bat file.

"C:\pathToAccess\MSACCESS.EXE" "C:\pathToDatabase\db.mdb" /REPAIR

Database repairs as expected, then shows the messge:

"Successfully repaired the ..." and you have to click "Ok" to get rid
of the message so that the database can close.

How does one suppress this message, so that the database shuts down
automatically?

I thought this switch was supposed to repair, then shutdown the
database without user intervention.

Any help is greatly appreciated! Thanks in advance!

[Tom van Stiphout]

On 25 Jun 2006 01:00:49 -0700, "ri*****@gmail.com" <ri*****@gmail.com>
wrote:

That's indeed annoying. Here is a work around that worked for me. Note
that in JetComp (and later versions of Access) there is no distinction
between repair and compact.
rem Not ideal because of 'success' messagebox "c:\program
files\microsoft office97\office\msaccess.exe" "c:\program
files\microsoft office97\office\samples\northwind.mdb" /repair
rem Next requires installation of JetComp from
http://support.microsoft.com/?kbid=295334
"c:\program files\microsoft office2000\jetcomp.exe" -src:"c:\program
files\microsoft office97\office\samples\northwind.mdb"
-dest:"c:\program files\microsoft
office97\office\samples\northwind2.mdb"
rem Todo: Delete the old file, and rename the new one.

-Tom.

I am running this command from a .bat file.

"C:\pathToAccess\MSACCESS.EXE" "C:\pathToDatabase\db.mdb" /REPAIR

Database repairs as expected, then shows the messge:

"Successfully repaired the ..." and you have to click "Ok" to get rid
of the message so that the database can close.

How does one suppress this message, so that the database shuts down
automatically?

I thought this switch was supposed to repair, then shutdown the
database without user intervention.

Any help is greatly appreciated! Thanks in advance!

[ritenah]

What a great and simple solution!

By chance is there a full list of syntax/switches/options for
jetcomp.exe?

Going to put this into a batch file I can invoke with AT.

Tom van Stiphout wrote:

On 25 Jun 2006 01:00:49 -0700, "ri*****@gmail.com" <ri*****@gmail.com>
wrote:

That's indeed annoying. Here is a work around that worked for me. Note
that in JetComp (and later versions of Access) there is no distinction
between repair and compact.
rem Not ideal because of 'success' messagebox "c:\program
files\microsoft office97\office\msaccess.exe" "c:\program
files\microsoft office97\office\samples\northwind.mdb" /repair
rem Next requires installation of JetComp from
http://support.microsoft.com/?kbid=295334
"c:\program files\microsoft office2000\jetcomp.exe" -src:"c:\program
files\microsoft office97\office\samples\northwind.mdb"
-dest:"c:\program files\microsoft
office97\office\samples\northwind2.mdb"
rem Todo: Delete the old file, and rename the new one.

-Tom.

I am running this command from a .bat file.

"C:\pathToAccess\MSACCESS.EXE" "C:\pathToDatabase\db.mdb" /REPAIR

Database repairs as expected, then shows the messge:

"Successfully repaired the ..." and you have to click "Ok" to get rid
of the message so that the database can close.

How does one suppress this message, so that the database shuts down
automatically?

I thought this switch was supposed to repair, then shutdown the
database without user intervention.

Any help is greatly appreciated! Thanks in advance!

[ritenah]

Ahh, nevermind, I found that doing a jetcom -? produces all the
information. As you can see I'm not from the Win world.

Thanks again though, this is great!

ri*****@gmail.com wrote:

What a great and simple solution!

By chance is there a full list of syntax/switches/options for
jetcomp.exe?

Going to put this into a batch file I can invoke with AT.

Tom van Stiphout wrote:

On 25 Jun 2006 01:00:49 -0700, "ri*****@gmail.com" <ri*****@gmail.com>
wrote:

That's indeed annoying. Here is a work around that worked for me. Note
that in JetComp (and later versions of Access) there is no distinction
between repair and compact.
rem Not ideal because of 'success' messagebox "c:\program
files\microsoft office97\office\msaccess.exe" "c:\program
files\microsoft office97\office\samples\northwind.mdb" /repair
rem Next requires installation of JetComp from
http://support.microsoft.com/?kbid=295334
"c:\program files\microsoft office2000\jetcomp.exe" -src:"c:\program
files\microsoft office97\office\samples\northwind.mdb"
-dest:"c:\program files\microsoft
office97\office\samples\northwind2.mdb"
rem Todo: Delete the old file, and rename the new one.

-Tom.

I am running this command from a .bat file.

"C:\pathToAccess\MSACCESS.EXE" "C:\pathToDatabase\db.mdb" /REPAIR

Database repairs as expected, then shows the messge:

"Successfully repaired the ..." and you have to click "Ok" to get rid
of the message so that the database can close.

How does one suppress this message, so that the database shuts down
automatically?

I thought this switch was supposed to repair, then shutdown the
database without user intervention.

Any help is greatly appreciated! Thanks in advance!

[Lyle Fairfield]

ri*****@gmail.com wrote:

I don't care about the philosophical war between "/repair" and
"/compact", or the historical developments of said commands.
Often, when one writes:

"Any help is greatly appreciated! Thanks in advance! "

one gets discussions of how and why things happen as they do.
I simply want to know if there is a way to FORCE the /repair switch to
function as the documentation states it should.

I guess we got confused about what

"How does one suppress this message, so that the database shuts down
automatically?
I thought this switch was supposed to repair, then shutdown the
database without user intervention."

means:

I guess when one posts to a public newsgroup where the emphasis of its
regulars is the investigation and sharing of knowledge about a
technical subject, and especially when one asks about an obsolete
version of the subject of the newsgroup, which most of us can no longer
test, one may not get what "I simply want".

Access has paid technical support. It's not as good as CDMA, of course,
but it may be more suitable for the "I simply want" part of your soul.

[ritenah]

Lyle,
I had a question. I did a search. I noticed a pattern. Since that
pattern revealed this particular question being outright avoided, I
framed my request accordingly.

Guess what. At least one other shared my concern, and frustration. I
got a beautifully well focused answer, that I'm using and loving as we
speak.

One last thing. I did not choose obsolescence in this particular
project. It choose me. One needs to eat. I am equally *nix and
windowed as far as my projects go, and this one just happened to
involve old technology. I don't mind at all.

Don't confuse a well focused, intensely framed question for anything
else. It was simply that. A question.

And yes. Thanks again!

Lyle Fairfield wrote:

ri*****@gmail.com wrote:

I don't care about the philosophical war between "/repair" and
"/compact", or the historical developments of said commands.

Often, when one writes:

"Any help is greatly appreciated! Thanks in advance! "

one gets discussions of how and why things happen as they do.

I simply want to know if there is a way to FORCE the /repair switch to
function as the documentation states it should.

I guess we got confused about what

"How does one suppress this message, so that the database shuts down
automatically?
I thought this switch was supposed to repair, then shutdown the
database without user intervention."

means:

I guess when one posts to a public newsgroup where the emphasis of its
regulars is the investigation and sharing of knowledge about a
technical subject, and especially when one asks about an obsolete
version of the subject of the newsgroup, which most of us can no longer
test, one may not get what "I simply want".

Access has paid technical support. It's not as good as CDMA, of course,
but it may be more suitable for the "I simply want" part of your soul.

[ritenah]

I got a nice chuckle reading that!
Verily, my soul is speaking to you through googlegroups!

Lyle Fairfield wrote:

but it may be more suitable for the "I simply want" part of your soul.

['69 Camaro]

Hi.

I don't care about the philosophical war between "/repair" and
"/compact", or the historical developments of said commands.
You should care with Access 97, because it doesn't have the safety feature
built in like the Jet 4.0 versions do, where the repair will be done if and
only if it needs to be done. Trying to repair an Access 97 database that
doesn't need to be repaired may result in a corrupted file that is
unrecoverable.

If Access 97 needs to be repaired, you will be prompted to do so.
Otherwise, if it's acting rather bizarrely, then you need to repair it. You
don't need to guess whether or not an Access 97 database file should be
repaired. Please see the following Web page for more information:

http://groups.google.com/group/comp....a501bdde2cae88

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/ex...ributors2.html for contact
info.
<ri*****@gmail.com> wrote in message
news:11**********************@c74g2000cwc.googlegr oups.com... Somewhat interestingly and funny, is that all the searching that I've
done about this specific question always amounted to the same scenario.

There was never an answer. People more commonly replied with a "why do
you want to do that anyway", which is hilarious.

If it is impossible to SUPRESS the informative pop-up message after
running a command-line "/repair" switch with Access 97, why not just
state that?

Even more funny is that "/repair" from the cli is described by
Microsoft as a command that is supposed to automatically close access
after completion.

I don't care about the philosophical war between "/repair" and
"/compact", or the historical developments of said commands.

I simply want to know if there is a way to FORCE the /repair switch to
function as the documentation states it should.

That's all. Thanks!

ri*****@gmail.com wrote:

I am running this command from a .bat file.

"C:\pathToAccess\MSACCESS.EXE" "C:\pathToDatabase\db.mdb" /REPAIR

Database repairs as expected, then shows the messge:

"Successfully repaired the ..." and you have to click "Ok" to get rid
of the message so that the database can close.

How does one suppress this message, so that the database shuts down
automatically?

I thought this switch was supposed to repair, then shutdown the
database without user intervention.

Any help is greatly appreciated! Thanks in advance!

[David W. Fenton]

"ri*****@gmail.com" <ri*****@gmail.com> wrote in
news:11**********************@i40g2000cwc.googlegr oups.com:

I am running this command from a .bat file.

"C:\pathToAccess\MSACCESS.EXE" "C:\pathToDatabase\db.mdb" /REPAIR

Database repairs as expected, then shows the messge:

"Successfully repaired the ..." and you have to click "Ok" to get
rid of the message so that the database can close.

How does one suppress this message, so that the database shuts
down automatically?

I thought this switch was supposed to repair, then shutdown the
database without user intervention.

What version of Jet are you doing this with? If it's Jet 4 or Jet
3.51, then you shouldn't be doing a repair by itself, anyway. Repair
by itself can damage an otherwise usable database beyond repair.
This is why with Jet 3.51 and the Access 97 SR1, compact was changed
to do a repair *if needed* before the compact, and the REPAIR
command by itself was severely deprecated.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[David W. Fenton]

"Lyle Fairfield" <ly***********@aim.com> wrote in
news:11**********************@c74g2000cwc.googlegr oups.com:

I guess when one posts to a public newsgroup where the emphasis of
its regulars is the investigation and sharing of knowledge about a
technical subject, and especially when one asks about an obsolete
version of the subject of the newsgroup, which most of us can no
longer test, one may not get what "I simply want".

Access 97 is not "obsolete" by any reasonable definition, Lyle. It
is just not the latest version.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[David W. Fenton]

"ri*****@gmail.com" <ri*****@gmail.com> wrote in
news:11**********************@c74g2000cwc.googlegr oups.com:

I don't care about the philosophical war between "/repair" and
"/compact", or the historical developments of said commands.
Microsoft cared enough about it to make REPAIR a part of the COMPACT
process when necessary, and severely deprecating any use of REPAIR
by itself. If you want to disregard Microsoft, then so be it, but
you're then embarking on nonsupported solutions.

So far as I can see, there's is no "philosophical war" between the
two. Microsoft made very clear than from Jet 3.51 and Access 97 SR1
that you should *never* use repair by itself because that could
damage your database beyond recovery.
I simply want to know if there is a way to FORCE the /repair
switch to function as the documentation states it should.

Who cares about something you shouldn't be doing in the first place?

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/