[AccessD] Weird problem after installing runtime A2K

While we are on the subject...slightly. I have noticed that the new version
of Access 2003 is stand-alone with run-time option. It is suppose to be a
few steps up from the older run-time-engines with all sorts of features that
support local extensions and a full deployment model. See
http://www.msdn.microsoft.com/office/technologyinfo/devtools/accessextension
s/default.aspx

The Royalty package, that will unlimited Royalty free distribution, can be
purchased though I could not find a price after a rudimentary scan.
Access2003 upgrade, from A97 forward, is $109.00US. Time to learn VB.NET(?)

Jim

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of MartyConnelly
Sent: Monday, June 07, 2004 9:02 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Weird problem after installing runtime A2K


Just a guess but assuming you created the runtime mdb with Access 2000
SP3, it maybe that there is an old
SP1 runtime on the machine, that hasn't been uninstalled or removed
properly. You might get away with
installing to a different directory or getting someone with admin status
on their machine to install it.
Test installing it to a non admin user on your development machine.
A lot of these problems can be resolved with using SageKey scripts and
Wise or Install Shield
for deployment.
http://www.sagekey.com

Annie Courchesne, CMA wrote:

>Hi group!
>
>I've recently installed a runtime version of Access 2000 (using Office
>developper).  On one computer, the following message is displayed :
>
>"Error 1706.  No Valid source could be found for product Microsoft Access
>2000 SR-1 Runtime.  The Windows installer cannot continue."
>
>That computer as Office 2003 Small business installed and is running under
>Win 2K Pro.  When we go to the Microsoft Update center, it suggests to
>update the runtime to SP-3.  The user does not have administrator status on
>that computer.
>
>If any of you out there ever had this problem, how did you solve it?  Would
>the update of the runtime solve the situation?
>
>I'll welcome any help!
>
>Thanks!
>
>
>Annie Courchesne, CMA
>
>
>
>

--
Marty Connelly
Victoria, B.C.
Canada



--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com