DataBase - deployment issues of Access XP, Access 2003, and Access 2003

Asked By gerry_lowry

10-Mar-08 01:17 AM

On my advice, a long time ago, a customer purchased the Access XP developer edition.

That special Office XP version of Access was supposed to allow the Access developers to deploy
Access XP applications within their organizations so that they did not have to purchase
retail Access (or Office Professional) for every workstation that used the Access applications.

Unfortunately, the deployment of Access XP did not work most of the time and the
customer was forced to purchase additional copies of Office for other computers.

The customer is annoyed and tired of having to do spend all this extra money because
on most of the computers, the end-user does not use Access.  Instead, the end-users
mostly use the Access applications and Outlook Express for sending e-mails.

Over the years, since Access XP, new versions of Access (2003, 2007) have come
from Microsoft.  The customer now has Access applications created under each
of these Access versions.

The customer has asked me to find out how the various Access projects can be
deployed so that it will no longer be necessary to continue buying Office software
that will not be used by the end-users.

Please advise.

Thank you.

g.

10-Mar-08 03:19 AM

Why didn't that work?  There could be a number of reasons and we can
likely give you solutions.


Without knowing what problems you are encountering that's way too
broad of a question.  Nevertheless see my Microsoft Access ODE or MOD
Runtime Installation Troubles Tips page at
http://www.granite.ab.ca/access/runtime.htm.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

10-Apr-08 01:11 AM

I have been successful distributing Access 2002 applications with the XP
developer's runtime by installing it with Wise Installbuilder and scripts
from Sagekey software: www.sagekey.com

Patrick.

On my advice, a long time ago, a customer purchased the Access XP developer
edition.

That special Office XP version of Access was supposed to allow the Access
developers to deploy
Access XP applications within their organizations so that they did not have
to purchase
retail Access (or Office Professional) for every workstation that used the
Access applications.

Unfortunately, the deployment of Access XP did not work most of the time and
the
customer was forced to purchase additional copies of Office for other
computers.

The customer is annoyed and tired of having to do spend all this extra money
because
on most of the computers, the end-user does not use Access.  Instead, the
end-users
mostly use the Access applications and Outlook Express for sending e-mails.

Over the years, since Access XP, new versions of Access (2003, 2007) have
come
from Microsoft.  The customer now has Access applications created under each
of these Access versions.

The customer has asked me to find out how the various Access projects can be
deployed so that it will no longer be necessary to continue buying Office
software
that will not be used by the end-users.

Please advise.

Thank you.

g.

20-Apr-08 03:13 AM

Patrick ... thank you ... did this always work for you?  If not, what are some of the issues with which you've had to deal.

g.

I have been successful distributing Access 2002 applications with the XP
developer's runtime by installing it with Wise Installbuilder and scripts
from Sagekey software: www.sagekey.com

Patrick.

On my advice, a long time ago, a customer purchased the Access XP developer
edition.

That special Office XP version of Access was supposed to allow the Access
developers to deploy
Access XP applications within their organizations so that they did not have
to purchase
retail Access (or Office Professional) for every workstation that used the
Access applications.

Unfortunately, the deployment of Access XP did not work most of the time and
the
customer was forced to purchase additional copies of Office for other
computers.

The customer is annoyed and tired of having to do spend all this extra money
because
on most of the computers, the end-user does not use Access.  Instead, the
end-users
mostly use the Access applications and Outlook Express for sending e-mails.

Over the years, since Access XP, new versions of Access (2003, 2007) have
come
from Microsoft.  The customer now has Access applications created under each
of these Access versions.

The customer has asked me to find out how the various Access projects can be
deployed so that it will no longer be necessary to continue buying Office
software
that will not be used by the end-users.

Please advise.

Thank you.

g.

20-Apr-08 03:17 AM

Hello Tony ... wish I could remember why.  It's been a while.
At this point, I think the customer's best option might be to
convert each Access application to Access 2007 so that
only one version would have to be distributed.  Microsoft
does not support every version for ever ... it would be
unfair to expect this ... OTOH, a version that deployed properly
in 2002 should still deploy properly under later flavours of MS operating systems.
Sadly, that's not always the case.

g.



Why didn't that work?  There could be a number of reasons and we can
likely give you solutions.


Without knowing what problems you are encountering that's way too
broad of a question.  Nevertheless see my Microsoft Access ODE or MOD
Runtime Installation Troubles Tips page at
http://www.granite.ab.ca/access/runtime.htm.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

23-Apr-08 11:18 AM

I have never had a problem distributing with SageKey scripts. The install
has worked every time. And having the Wise Installer allows me to use it for
other applications that don't involve the runtime.

Patrick.


Patrick ... thank you ... did this always work for you?  If not, what are
some of the issues with which you've had to deal.

g.

I have been successful distributing Access 2002 applications with the XP
developer's runtime by installing it with Wise Installbuilder and scripts
from Sagekey software: www.sagekey.com

Patrick.

On my advice, a long time ago, a customer purchased the Access XP developer
edition.

That special Office XP version of Access was supposed to allow the Access
developers to deploy
Access XP applications within their organizations so that they did not have
to purchase
retail Access (or Office Professional) for every workstation that used the
Access applications.

Unfortunately, the deployment of Access XP did not work most of the time and
the
customer was forced to purchase additional copies of Office for other
computers.

The customer is annoyed and tired of having to do spend all this extra money
because
on most of the computers, the end-user does not use Access.  Instead, the
end-users
mostly use the Access applications and Outlook Express for sending e-mails.

Over the years, since Access XP, new versions of Access (2003, 2007) have
come
from Microsoft.  The customer now has Access applications created under each
of these Access versions.

The customer has asked me to find out how the various Access projects can be
deployed so that it will no longer be necessary to continue buying Office
software
that will not be used by the end-users.

Please advise.

Thank you.

g.

10-Jun-08 08:37 PM

One issue we've had is trying to deploy the AccessXP Runtime SP3. With much
fooling around we've been able to get it to install on our Windows XP
clients. However we can't get it to install on our Terminal Server. The
error looks like this:

MSI (s) (28:94) [11:21:31:347]: Final Patch Application Order:
MSI (s) (28:94) [11:21:31:347]: Other Patches:
MSI (s) (28:94) [11:21:31:347]: Unknown\Absent:
{958C8EDE-2503-4813-BBD3-9EC1EE6788E8} - C:\Documents and
Settings\administrator.MEDICARD\Application
Data\OfficeUpdate12\Cabs\511518\511518.ARTSP3ff.msp
MSI (s) (28:94) [11:21:31:363]: Product: Microsoft Access 2002 Runtime -
Update '{958C8EDE-2503-4813-BBD3-9EC1EE6788E8}' could not be installed.
Error code 1642. Additional information is available in the log file
C:\Documents and Settings\administrator.MEDICARD\Application
Data\OfficeUpdate12\Temp\OU_MSI_511518_(00017).log.

MSI (s) (28:94) [11:21:31:363]: Product: Microsoft Access 2002 Runtime --
Installation failed.

The upgrade patch cannot be installed by the Windows Installer service
because the program to be upgraded may be missing, or the upgrade patch may
update a different version of the program. Verify that the program to be
upgraded exists on your computer and that you have the correct upgrade
patch.

C:\WINDOWS\Installer\3fd32b5.msi




I have been successful distributing Access 2002 applications with the XP
developer's runtime by installing it with Wise Installbuilder and scripts
from Sagekey software: www.sagekey.com

Patrick.

On my advice, a long time ago, a customer purchased the Access XP developer
edition.

That special Office XP version of Access was supposed to allow the Access
developers to deploy
Access XP applications within their organizations so that they did not have
to purchase
retail Access (or Office Professional) for every workstation that used the
Access applications.

Unfortunately, the deployment of Access XP did not work most of the time and
the
customer was forced to purchase additional copies of Office for other
computers.

The customer is annoyed and tired of having to do spend all this extra money
because
on most of the computers, the end-user does not use Access.  Instead, the
end-users
mostly use the Access applications and Outlook Express for sending e-mails.

Over the years, since Access XP, new versions of Access (2003, 2007) have
come
from Microsoft.  The customer now has Access applications created under each
of these Access versions.

The customer has asked me to find out how the various Access projects can be
deployed so that it will no longer be necessary to continue buying Office
software
that will not be used by the end-users.

Please advise.

Thank you.

g.