|
Hi all,
I'm trying to make a simple script to open Microsoft Access and a database file. I had used just a batch file, with the following command:
"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" C:\path\filename.mdb
This almost worked. It opens the application, but the command window remains open until you close Access, then the batch file carries on and finishes. I didn't want to have a batch file/command window left open the whole time.
So, I thought I would just do a simple Kix script to solve the problem:
RUN "C:\Program Files\Microsoft Office\Office\MSACCESS.EXE C:\path\filename.mdb"
The script almost works fine. It runs through the script and closes itself, which is great. But it always opens Access in a restored size, not maximized. I've tried opening the database manually, maximizing it, then opening it again manually and it stays maximized. But as soon as I run the script, it opens restored again. This is a pain.
I've searched through a number of posts on here to do with maximizing, and found ways to maximize the kix console window and other applications, but there doesn't appear to be an answer.
I've tried using the SHELL command, as suggested in an earlier post:
SHELL "START /MAX MSACCESS.EXE"
Which didn't open access. So I tried:
SHELL "c:\program files\microsoft office\office\msaccess.exe"
Which opened Access, but it didn't recognise the START /MAX command. And, by using the SHELL command, the script acts like a batch file so the console window stays open until Access has been closed.
So, i'm hoping you guys might know a way to force Access to start maximized. Preferably something to stick on the end of this semi-working Kix command:
RUN "C:\Program Files\Microsoft Office\Office\MSACCESS.EXE C:\path\filename.mdb"
Any help would be very much appreciated.
Thanks.
|