/Cmd and Server 2003

[Guest]

Hi, all!

Have been successfully using an Access 2002 database to run a manual update
of customer data on my workstation. I called it by using a shortcut
containing /cmd "XXX" as a parameter and by using "myStr = Command()" to
retrieve the parameter. It worked great.

We recently installed a new server running Server 2003 with Access 2002
installed. We copied the database (also 2002) to it, and have been trying to
schedule the same routine to run there automatically, but it will not
interpret the command line parameter. It also fails when simply
double-clicking the shortcut, so it's not the Scheduler. When I display the
retrieved value of the Command using a message box, it shows an empty string.

Some research in this Access discussion group showed a different format for
the parameter, "\cmdXXX" (no spaces or quotes) and using the Command$
function. We've tried that, and it doesn't work on the new server, either,
but works on my workstation.

Does Server 2003 not allow command line parameters, or am I doing something
wrong, here?

Thanks for the help,
Bruce

 

[Douglas J. Steele]

Are you remembering to include msaccess.exe in the shortcut?

/cmd is a command line parameter for the executable. If you only have the
mdb (or mde) in the shortcut, non of the command line arguments will be
used.

 

[Guest]

Guess I'm a Dee Dee Dee! Duh! Nope, we weren't.
Thanks, Douglas.
Bruce