Package Wizard / if user has Access 97?

[Guest]

Hi,

I created a setup.exe file for my Access 2003 App. I tried to install
the setup.exe on a computer that has Access 97, and the setup failed
w/ the message:

"can't find the dynamic-link library (DLL) mso97rt"

It's looking for the MS Access 97 run-time version instead of the
one I included in the setup.exe file.

isn't Access smart enough to get around the fact that users
will have different versions of Access?

Should I NOT include the Access 2003 runtime in my
setup.exe?

Thanks-

 

[Albert D. Kallal]

Hi,

I created a setup.exe file for my Access 2003 App. I tried to install
the setup.exe on a computer that has Access 97, and the setup failed
w/ the message:

"can't find the dynamic-link library (DLL) mso97rt"

It's looking for the MS Access 97 run-time version instead of the
one I included in the setup.exe file.

Hum, you are talking about the a2003 package wizard?

Is this failure during the install, or when you try and run the application?

Also, how far does the install get? (does it start at all?).

You of course did check the box to include the ms-access runtime (you do
mention this), and you should also use/set the shortcut option(s) to create
a shortcut to launch the application.

 

[Guest]

Well the setup.exe file is created fine. The problem is when
I run the setup.exe on another computer that has Access 97
installed. The app tries to open using Access 97, that is
where the error msg is coming from. Someone else in this
forum suggested to rename the msaccess.srg file, but this
isn't a valid option for mass distribution.

Thanks for any help.

 

[Albert D. Kallal]

Ok, I also asked one other question:

Do you use a shortcut to launch the application?

If you setup a shortcut, then your problem will go away.....

 

[Guest]

Hi,

I do have a short-cut. The problem is the Package Wizard
SHOULD put the access 2003 runtime version in

c:/program files/microsoft office/office11/msaccess.exe,

and this is what the shortcut says in the properties section,
but when I open the application on the target machine,
the machine cannot find the folder /OFFICE11 because
it doesn't exist. For some reason, it's not being created
via the Wizard.

Thanks.

 

[Guest]

Hi,

I figured it out. I am running the Package Wizard on Windows XP Professional,
but my target machine is Windows 2000. So, the Package Wizard put the
Access 2003 runtime version in :

"c:/program files/microsoft office XP/office11/msaccess.exe"

but the shortcut it created did not pick up the XP portion -- the shortcut
had:

"c:/program files/microsoft office/office11/msaccess.exe".

Maybe there is somewhere in the Package Wizard where I can tell
it which version of Windows to target so the shortcut will be
created correctly. I'll keep looking...

thanks,
Christy.

 

[Albert D. Kallal]

Hi,

I figured it out. I am running the Package Wizard on Windows XP
Professional,
but my target machine is Windows 2000. So, the Package Wizard put the
Access 2003 runtime version in :

"c:/program files/microsoft office XP/office11/msaccess.exe"

but the shortcut it created did not pick up the XP portion -- the shortcut
had:

"c:/program files/microsoft office/office11/msaccess.exe".

Maybe there is somewhere in the Package Wizard where I can tell
it which version of Windows to target so the shortcut will be
created correctly. I'll keep looking...

Yes, you have just discovered a bug in the p & d. What happened is that user
choose a *different* default install directory for office. Normally, all
versions of office install to:

c:\program files\microsoft office\

However, the wizard is smart enough figure out where the office install dir
is..so the wizard SHOULD be smart enough to make the correct shortcut..and
obviously in your case it does not.

I am also looking for a fix for this, and have submitted this to MS already.

I think the only workaround right now would be to purchase a commercial
install script. You can find them here:

www.sagekey.com


Another workaround would be to make a script that grabs the default office
dir..and then makes the shortcut. I am in need of this script...and will
write one asap.

 

[Guest]

Hi Albert,

Thank you very much for your posts- they were most helpful.
I may investigate SageKey; do you know if they get around
the multiple Access version problem? (if user has previous
version of Access, I still want the Access 2003 runtime to
run). i"ll contact them too to find out.

Thanks,
Christy.

 

[Albert D. Kallal]

Hi Albert,

Thank you very much for your posts- they were most helpful.
I may investigate SageKey; do you know if they get around
the multiple Access version problem? (if user has previous
version of Access, I still want the Access 2003 runtime to
run). i"ll contact them too to find out.

Yes, there stuff does solve the above problem.

As mentioned, if the shortcut "did" work right..then in a lot of cases the
standard package wizard would be fine..but in other cases, it still can
cause problems.

So, even if the shortcut bug gets fixed, you can STILL have problems if some
of your users have other versions of office installed. If you are looking
for a "trouble free" experience here...you will have to go with sagekey...

 

[Guest]

hi Albert,

thank you.....

have you ever used InstallShield Express? I am now trying
to include Access 2003 runtime in my InstallShield but don't
know how. InstallShield Express 4.0 only has selections
for Access 97 and 2000/2002. (not 2003).

Is there some way to isolate the Access 2003 runtime
merge module? the .msm file? I can then include this
in InstallShield.

thanks!
christy

 

[Albert D. Kallal]

hi Albert,

thank you.....

have you ever used InstallShield Express?

I played with InstallShield..but have no experience with the product.

I am now trying
to include Access 2003 runtime in my InstallShield but don't
know how. InstallShield Express 4.0 only has selections
for Access 97 and 2000/2002. (not 2003).

Is there some way to isolate the Access 2003 runtime
merge module?

I don't see why you can't take the runtime install folder from the office
2003, and use that. Remember, the runtime install files are included on the
office 2003 disk. the Developer edition simply gives you the "right" legally
to distribute the runtime files (but, they been there all along on the
office cd). Most, if not all software installs, be it word, excel, or
whatever do have "silent" install options, and also do have admin type
installs for system admins to deploy these applications via SMS (systems
management system). So, if you have experience installing this stuff, then I
suspect you could quite easily build some scripts in installshield to do
what the wizard does. And, just like you wrote your own software as opposed
to purchasing it..the same issue arises here!

Do you want to sit down and learn how to setup/make your own installs, or
use the p & d wizard, or purchase a MSI script from sagekey. The choice here
is yours!.

I am also looking to fix the p & d wizard bug. Do note that ALL of the
source of the wizard is included with the developers edition. (you do
realize that the p & d wizard is written in ms-access....and the source code
IS included). So, either you write your own installshief scripts, or look at
the source in the ms-access p & d...or pick up the phone and call
sagekey......

 

[Guest]

hi Albert,

Just to follow-up, I called SAGEKEY and ordered
the Access 2003 MSI Wizard, and am glad I did.

But- I can't seem to find my ACCESSRT.CAB file,
which I need. I have Access 2003 via an upgrade
purchase, so my ACCESSRT.MSI file isn't where
it "should" be and I can't find a ACCESSRT.CAB file,
which SAGEKEY says it needs.

Any ideas?

Thanks,
Christy Warner.