[AccessD] A2K MDE Runtime Reference problem - URGENT

Jim DeMarco Jdemarco at hudsonhealthplan.org
Mon Mar 1 08:13:08 CST 2004


Gustav,

The real mystery is that we have not changed or added any references.  It just seems the date fields that have the problem.

Thanks,

Jim DeMarco

-----Original Message-----
From: Gustav Brock [mailto:gustav at cactus.dk]
Sent: Monday, March 01, 2004 8:52 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] A2K MDE Runtime Reference problem - URGENT


Hi Jim

One source for the error may be that the default name for the Windows
directory is WinNT in WinNT/2000 but Windows in Win 9x and Win XP.

But what were the references in the original MDE? Does that MDE run
under WinXP? If so, can you modify your MDE to have references as
those of the original MDE?

Or you could create a c:\windows folder on your Win2000 machine, copy
the libraries to this and adjust your references before creating the
MDE.

Or you could follow the advice of Charlotte, I believe, and move your
libraries to the folder of your installed MDE; but that would require
an adjustment of your install script and you wanted to avoid that,
right?

/gustav


> We have an open source app that we've modified and are installing at various doctor's offices in the area.  The application came with an installation routine that installs the A2K runtime and the
> app MDE.  We use the install the app came with then overwrite the app MDE with our modified version.  The application runs fine in-house after overwriting the MDE (Win2K) but on a contractor's
> machine (WinXP) and a client's machine (Win98) we're losing a library reference (Date displays and functions calling Date functions fail with #Name? error).  Since it's an MDE we can't see or
> adjust the references (or can we?).  Does anyone know how we can get the references straightened out?  Are the client machines missing a DLL by chance?.

> I've been attempting to create our own install package using InstallShield but it's looking for an *.msi file for the Access Runtime.  I'm not sure where to find that either.  I'm also not really
> sure a fresh install package will fix the reference problem anyway.

> TIA,

> Jim DeMarco
> Director Product Development
> Hudson Health Plan

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



More information about the AccessD mailing list