[AccessD] Windows 2000 Professional, Access 2000 Runtime on Windows XP

Well you could develop your Access 2000 runtime on an XP box.
Going to Access 2003 will give you a few more headaches as you will have 
to handle Access Macro Security with 2003 yourself.
The Access 2003 sagekey scripts have a way of disabling macro security 
for a specific install without using a certificate store.
For one site I had someone write a quick and dirty VB program to startup 
up access with 2003 macro security disabled..
With SageKey you are essentially paying for the testing of  their 
product with a myriad of OS and Access permutations.
You could buy just the MSI installer scripts from SageKey if you have a 
vanilla install, ie. no multiple OCX's to be installed as well.
Cheaper than buying Install Shield or Wise with the scripts.
Ask sagekey about it.
Why don't you phone SageKey  (888) 248-0055 Tollfree
They are in British Columbia and speak Canadian ;).

Nicholson, Karen wrote:

>My user is in California, so I will have to wait for him to get to work
>to find out.  I will post back later.  It is not just me.... Hmmm.
>Sagekey anyone?
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mike & Doris
>Manning
>Sent: Tuesday, November 30, 2004 9:24 AM
>To: 'Access Developers discussion and problem solving'
>Subject: RE: [AccessD] Windows 2000 Professional,Access 2000 Runtime on
>Windows XP
>
>
>We had similar problems doing installs on Windows XP machines.  What
>files
>is it prompting them to get so I can check my notes?
>
>Doris Manning
>Database Administrator
>Hargrove Inc.
>www.hargroveinc.com
>
>
>-----Original Message-----
>From: accessd-bounces at databaseadvisors.com
>[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Nicholson,
>Karen
>Sent: Tuesday, November 30, 2004 8: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.
>  
>

-- 
Marty Connelly
Victoria, B.C.
Canada