[AccessD] A2K MDE Runtime Reference problem - URGENT

Gustav Brock gustav at cactus.dk
Mon Mar 1 09:33:45 CST 2004


Hi Jim

Maybe your client installed it without Administrator rights - which
you probably did?

/gustav


> I just installed on an XP system here and the app worked.  Some read-only issues that I believe relate to security on the machine I was on but the date functions all worked.

> I seem to recall some code in the archives that set references.  I'll take a look there and see what comes up.

> Thanks again,

> Jim D.

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


> Hi Jim

> The Date fields are the symptom only.
> The cure is to locate and reestablish one or more missing reference.

> Access will - and is quite good at it but not perfect - try to locate
> any missing reference in the current environment, thus adjusting the
> path for each of these references.
> Maybe Access succeeded when the MDE was moved to your platform
> (Win2000 and C:\WINNT) but failed when it moved "back" (Win 9x/XP and
> C:\Windows) at the clients.

> /gustav

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




More information about the AccessD mailing list