Avatar of Fabrice Lambert
Fabrice Lambert
Flag for France asked on

Command line troubles

Hi,

When launching an access database from the command line, one of my user experience a weird behavior.

The database is supposed to recieve a command line like the following (value returned by the Command() function):
import="291" database="C:\Users\userName\My documents\Application_DATA.accdb"

But he recieve:
import= 291 database= C:\Users\userName\My documents\Application_DATA.accdb
Quotes are stripped, and an additional space is inserted right after the "=" sign (or quotes are replaced by a space).

Do you see anyhing that can explain this behavior ?
Microsoft Access

Avatar of undefined
Last Comment
Fabrice Lambert

8/22/2022 - Mon
als315

Is it shortcut, cmd file, copy/paste to command line? Could you show full string?
Fabrice Lambert

ASKER
The command line comes from a batch:
"C:\Program Files (x86)\Microsoft Office\Root\Office16\msaccess.exe" "C:\Users\userName\My documents\Application_PRG.accdb" /cmd import="291" database="C:\Users\userName\My documents\Application_DATA.accdb"

Open in new window

The database is opened fine, but the code parsing the command line fail because the value returned by the Command() function does not have the expected pattern.
als315

Quotes in command line means it is text part and it will be delivered without quotes.
I don't believe it is working anywhere.
Try
/cmd "import=291" "database=C:\Users\userName\My documents\Application_DATA.accdb"
from command you should get two parameters:
import=291
and
database=C:\Users\userName\My documents\Application_DATA.accdb
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
Fabrice Lambert

ASKER
@als315: Afraid not. As I stated, I recieve the command line as expected, but one user don't.
From my knowledge, Access is supposed to forward the whole string following the /cmd argument untouched.
And the Command() function return a string, not a container.
als315

I can't test your command now, will do it later today, but Access can get more then one parameter, divided by space, like this:
/cmd "Parm1" "Parm2"
You can try:
/cmd "import=""291""" "database=""C:\Users\userName\My documents\Application_DATA.accdb"""
als315

I don't understand also why you need quotes around parameter
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
als315

May be this is correct:
/cmd "import=""291"" database=""C:\Users\userName\My documents\Application_DATA.accdb"""
Fabrice Lambert

ASKER
The issue is:
Why on one computer the command line is forwarded intact, and why on the 2nd computer it is not.

Notes:
Quotes in command line means it is text part and it will be delivered without quotes.
This is false.
Applications recieve command line as string, quotes are here to handle spaces. It is up to their parsing functionality to tanstype values or do whatever they want with it.
Scott McDaniel (EE MVE )

Anything different about the machine? Like a different language, etc?

Can you try logging into that machine as a different user and see if the same behavior exists? If it does not, then try logging in as the "trouble" user on a different machine - does the behavior follow the user?

I ask because I had a similar experience many years ago with an Access database and the Command function, and traced it down to a bad user profile. I'm not sure how the user profile has anything to do with that, but once I created a new user profile, the issue went away.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
Fabrice Lambert

ASKER
User is somewhat busy today, we'll try tomorow (me logging on his computer and vice-versa).
als315

Sorry, Fabrice, I was wrong, you were correct. New knowledge, thanks. Never see before that you can't send 2 parameters one by one:
/cmd "Param1" "Param2"
but
/cmd i="Param1" j="Param2"
is possible.
Looks like there is some undocumented interpreter.
Fabrice Lambert

ASKER
Well, no luck with logging on his computer.

No explanations still, I suspect something on computer's environent (go figure what with limited privilèges).
Doubling double quotes fixed the issue, even tho, I do not like it because we have an heterogenous command line.
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Scott McDaniel (EE MVE )

I'd agree with the environment issue, and with things like this you'll have a hard time sussing it out.

An Office repair or reinstall may resolve the issue, but that would be a last-ditch effort.
ASKER CERTIFIED SOLUTION
Fabrice Lambert

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.