MLH wrote:
Of course, dbl-clicking the runtime application icon on the
desktop now results in MS Access 97 splash screen being
displayed during the launch. That will go away after I remove
the copy of A97 I installed onto the Win98 box, I'm sure. But
I really would like to know how to circumvent this behavior,
as it catches me by surprise sometimes when I install a runtime
app onto a customer machine already having A97 installed.
My application icon Target: string looks like this...
"C:\Program Files\TowPack\TowPack.mde"
and its Start In: string like this...
"C:\Program Files\TowPack"
I'm certain the installation of A97 changed the file association
for mde files to be launched with A97's msaccess.exe in
C:\Program Files\Microsoft Office\Office\ instead of whatever
it was using before. So, how could I modify my runtime app's
Target: string to launch the way it was launching before I
installed A97 last night?
Unless you go to some length to prevent it you won't have two separate instances
of the MSAccess.exe file on the machine. The runtime installer will not install
the runtime if Access 97 is already present and the Office 97 installer will use
the same folder and file that the runtime created if the runtime install is done
first.
What you need is the /Runtime command line argument in your shortcut if you want
the app to run in the "runtime environment" even when a fully licensed copy is
present.
If you place your own BMP file in the same folder as your mdb and give it the
same name as your mdb (other than extension) then it will display that when you
app is opened instead of the Office splash screen.
As stated previously you need to recreate your setup package and use the options
provided for a proper shortcut to be created. It should not simply be a
shortcut pointing at the mdb file.
--
I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com