[AccessD] Broken References in Runtime AXP

I tested it and it works but we would have to figure out how to make it
run just once to fix the reference and then disable it going forward.
The delay is significant, and I'm running a fast machine, which many of
our customers aren't.

Charlotte Foust

-----Original Message-----
From: Gustav Brock [mailto:gustav at cactus.dk] 
Sent: Monday, July 21, 2003 10:50 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Broken References in Runtime AXP


Hi Charlotte

Did you try to apply my Function VerifyReferences() - or similar - which
I posted earlier?

The problem is that Access believes the references are OK but at least
one turns out not to be.

This bug is a bummer and it is unbelievable that MS has allowed it to
survive since A97 - or probably since A95. 

It would be nice if someone working with Access 2003 beta could report
back to MS if the bug still exists. I am, however, fully aware that it
will take quite some time to test this ...

/gustav


> The reference resolves using the RefLibPaths key.  Unfortunately, I'm 
> still getting a #Name? Error on a control bound to the expression 
> Format(Date(),"dd-mmm-yyyy").  Any other suggestions.

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