Doug Murphy
dw-murphy at cox.net
Tue Nov 30 11:09:53 CST 2004
Karen,
We have a product developed in Access XP that we sell. I built the install
with Wise installer 9 and the associated Sagekey scripts. We have had not
experienced the problem you describe. I have tested our installation
package on as many operating systems and different configurations of these
systems as I can come up with and all seem to work. I'd recommend going the
Wise/Install shield Sagekey route.
Another benefit of using the Sagekey scripts is that you can download from
Sagekey all the ancillary files required for installation in one package.
When you use the Developer deployment wizard it pulls the files from your
computer and you may run into versioning problems.
Doug
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Nicholson, Karen
Sent: Tuesday, November 30, 2004 5:12 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Windows 2000 Professional,Access 2000 Runtime on Windows
XP
This runtime issue is starting to drive me a little bonkers. I am running
Windows 2000 Professional, using the Access 2000 runtime deployment wizard
and now my manufacturers who just have plain old XP are not able to run my
runtime installation package. The package is prompting the user to get
files that it does not have and then their system boots.
Has anyone had this problem? What are my options? Will upgrading to Access
2003/Deployment Wizard solve the XP problem when I am developing on Windows
2000 Professional?
About SageKey - is this product good enough to take all the operating
systems and Access versions off the table and just run a clean installation
of the runtime package?
SO: A) - Upgrade to Access 2003/Deployment Wizard
B) - Do the SageKey
Opinions, please?
Thanks.
--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com