Message Code Causing PC Error

[TheScullster]

Hi all

We have an Access 2000 database with which I am vaguely familiar running
under Access/Office2003.
A second Access application written by Peter De Baets is used to compact the
back end of this database.
Within the code of this compact utility (of which I have very little
knowledge) there is a function to alert me of the success or failure of the
compact operation. This function appears to be a later addition by a n
other.

The relevant lines are as follows:

If strMsg = "Compact Errors as follows:" & Chr(13) Then strMsg = " No
Compact Error!"
Call Shell(Environ$("COMSPEC") & " /c net send " & Me.adm & " " & strMsg,
vbNormalFocus)

This alert message stopped working many moons ago, but as the status is
easily checked on the database results form, it wasn't an earth shattering
loss.

Now, however, each time this compact utility runs, I receive a command
window error message:

"The command contains an invalid number of arguments.
More help is available by typing Net Helpmsg 3503."

This is accompanied by a Windows error message:

"Net Command has experienced a problem and needs to close. We are sorry for
the inconvenience."

Can anyone explain why this error has arisen?
The compact utility has not been altered in any way.

Thanks in anticipation

Phil

 

[Guest]

It's a problem with Terminal Server. There's a little info at:
http://support.microsoft.com/kb/186546

My suggestion is to turn off the automatic compacting and repair. It's one
of those things people do to excess and with no real benefit.

 

[TheScullster]

It's a problem with Terminal Server. There's a little info at:
http://support.microsoft.com/kb/186546

My suggestion is to turn off the automatic compacting and repair. It's one
of those things people do to excess and with no real benefit.

Thanks Jerry, but I was hoping to understand why this utility had started
failing after years of faultless operation.

Phil