[AccessD] Broken References in Runtime AXP

Hi Charlotte

I absolutely understand that - but maybe you don't have a choice.

I've tried to simulate your situation in A97 but failed as A97 have
(for those scenarios I have been able to establish) always been too
smart to locate the references without being forced to.

It could be very interesting to learn if your current situation would
be corrected by this trick as it was my understanding that it should
NOT be necessary or needed with Access XP.

/gustav


> But we don't want to run this at every startup, Gustav.  We only want to
> fix a reference if it is broken and even that delays the load of the
> startup form.

> Charlotte Foust

> -----Original Message-----
> From: Gustav Brock [mailto:gustav at cactus.dk] 
> Sent: Friday, July 18, 2003 8:52 AM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] Broken References in Runtime AXP


> Hi Charlotte

>> ..  In fact we started out putting the code library in the same folder

>> with the application.  Guess what?  When the app was installed in a 
>> different folder from the one the setup was created from, Access found

>> the file and did not report a broken reference but strange things 
>> happened that were only cured by unchecking and resetting the 
>> reference.

> This is why you could/should run the function in my previous message
> which effectively kicks the a.. of Access.

> It removes the top reference, shifts the remainders one step up and adds
> the reference back. This should make no difference to your app except if
> you have duplicated function names in the references libraries which I
> doubt you have.