Ok...I'll bite...despite a big white empty area!!!
If you just need to start ms-access, or a given "file" of you choice, then a
batch file is fine
The above command at the windows prompt will thus launch the file of your
choice as if you had clicked on it....
However, if you need more control, or want to run a particular piece of
code, and then shutdown ms-access, then likely a windows script would be a
msgbox "Click ok to run batch job",64
set accessApp = createObject("Access.Application")Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=9507
accessApp.OpenCurrentDataBase("C:\Documents and Settings\Albert\My
set accessApp = nothing
msgbox "Job complete", 64
The above would launch ms-access, and then run/execute a pub sub called
TimeUpDate in a standard module. The application is then quit.
So, a windows script is somewhat more flexibility, as you don't have to
'quit' the application in code after you run a routine of your choice....
If you just need to launch a particular .doc, pdf, or in your case mdb
file...use the "start" command at the windows prompt, or a .bat file. If you
need the 2nd case where you want to run some code inside of the mdb..and
then quit...use the 2nd windows script example. It is not clear which
scenario you need...but, then again, that comes back to you not using the
big white space to further give details about what you need...(so, I was
either forced to skip your question, or write a *longer* post guessing as to
what/which scenario you are looking for).
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada pleaseNOOSpamKallal@msn.comReference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=9507 http://www.members.shaw.ca/AlbertKallal