jimdettman at verizon.net
Wed Apr 13 05:42:25 CDT 2022
It's because of the spaces in the path. Anytime you have a space in the
path, it must be enclosed in quotes when it's in a batch file:
"C:\Program Files (x86)\Microsoft Office\root\Office16\MSACCESS.EXE"
From: AccessD On Behalf Of John Colby
Sent: Tuesday, April 12, 2022 9:04 PM
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>; John W Colby <jwcolby at gmail.com>
Subject: [AccessD] \decompile
In the past I always created a batch file to perform a \decompile when I
opened Access. I don't have that now so I am creating one. I found the
syntax out on FMS as follows:
"C:\Program Files (x86)\Microsoft Office\root\Office16\MSACCESS.EXE
where the path depends on your instance of Office. This is in fact my
If I open the command window and paste that in it returns an error message
"The directory name is invalid". If I perform a CD C:\Program Files
(x86)\Microsoft Office\root\Office16 it does in fact change directory into
that path and from there a MSACCESS.EXE /decompile opens access.
So what gives? Majorly confused on this part.
Is it possible to do the same thing with a shortcut to Access? I created
the shortcut and placed the /decompile inside of the quotations and Access
opens, however there is no obvious way to determine whether the /decompile
is passed in to the access instance. I vaguely remember that this is the
method that I used in the past.
I assume that some of you guys do this stuff?
John W. Colby
AccessD mailing list
AccessD at databaseadvisors.com
More information about the AccessD