Command line troubles

Fabrice Lambert
Fabrice Lambert used Ask the Experts™
on
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 ?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Is it shortcut, cmd file, copy/paste to command line? Could you show full string?
Fabrice LambertConsulting
Distinguished Expert 2017

Author

Commented:
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.
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
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Fabrice LambertConsulting
Distinguished Expert 2017

Author

Commented:
@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.
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"""
I don't understand also why you need quotes around parameter
May be this is correct:
/cmd "import=""291"" database=""C:\Users\userName\My documents\Application_DATA.accdb"""
Fabrice LambertConsulting
Distinguished Expert 2017

Author

Commented:
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.
Most Valuable Expert 2012
Top Expert 2014

Commented:
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.
Fabrice LambertConsulting
Distinguished Expert 2017

Author

Commented:
User is somewhat busy today, we'll try tomorow (me logging on his computer and vice-versa).
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 LambertConsulting
Distinguished Expert 2017

Author

Commented:
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.
Most Valuable Expert 2012
Top Expert 2014

Commented:
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.
Consulting
Distinguished Expert 2017
Commented:
An Office repair or reinstall may resolve the issue, but that would be a last-ditch effort.
Alas, not my responsibility.
Thanks for the input tho.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial