MSAccess 'Command Line' error w/run-time app

[MRISTS]

I have 2 versions of an Access run-time app. One is packaged using Access 2000, the other is Access 97. A user who does not have any full version of Access, has a Win98 machine with Office 97, installed the 2000 version of the app. The app wouldn't run. She uninstalled (using Add/Remove Programs), we search for all MSACCESSS files and installed the 97 version. She receives the following error:

The command line you used to start Microsoft Access contains an option that Microsoft Access doesn't recognize.

Exit and restart Microsoft Access using valid command-line options.


The MS KnowledgeBase indicated that the database may have a space in the name, it does not. It also suggests installing the developer's addition of Access. As this user does not have any version of Access this is not an option. Any help would be appreciated.

 

[tlbroadbent]

Have you analyzed the command line in the shortcut that she uses to start the application? Have you verified the options used are valid in Access 97?

If you are unable to determine the cause of the error, please post the shortcut used to start the application so we can analyze the command line? Terry L. Broadbent
FAQ183-874 contains tips for posting questions in these forums.
NOTE: Reference to the FAQ is not directed at any individual.

 

[MRISTS]

Here is the shotcut target. We appreciate your assistance with this, we're really at an impass here.

"C:\Program Files\SettlementX\setup\32AUTOLE.DLL" /runtime /wrkgrp "C:\WINDOWS\SYSTEM\WRKAPP.MDW" "C:\Program Files\SettlementX\SettleX.mde" /User Agents /Pwd 4buy10house

 

[UncleJack]

Your command line seems to be defective. The first part of the command line, as I understand it, should be the path and name of the executable, e.g. "C:\Program Files\Msaccess.exe"

The general format of the command line is:

“Path & Msaccess.exe” /excl /runtime /other options /profile “Named Profile” /wrkgrp “path and name of .mdw file” “Path and name of .mdb or .mde file”

It does strike me a bit odd that you seem to be using both user level security and an .mde file. Usually we think of those as an either/or situation.

The M/S ODE setup package as provided in the developer's version of A2K or A97 has a number of bugs that severely limit its utility in a commercial application. I used on an application I provided for free to a group of about 75 users across the country and had no significant problems with it. But on other commercial applications it proved to be unacceptable. I suggest you have a look at

http://www.sagekey.com

for more information on this topic.

Uncle Jack