[AccessD] Broken References in Runtime AXP

As a followup, I tried using RefLibPaths and it was no use either in
runtime.  The problem seems to be that the code is simply not being run,
although I followed Michael Kaplin's advice and put it into a separate
module, carefully disambiguated and called it from an autoexec macro
before opening any forms, etc.  It just doesn't seem to execute at all
under the runtime engine.  I even tried setting a reference to the
extensibility library so I can use the VBIDE object in the code and had
the same results with it.  I'm rapidly losing what's left of my mind.
This is a regular mdb, not an mde.

Charlotte Foust

-----Original Message-----
From: Charlotte Foust 
Sent: Thursday, July 17, 2003 7:00 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Broken References in Runtime AXP


That's what I meant, Shamil, and I had looked at the RefLibPaths
infromation, but since this is a commercial application, creating custom
profiles may not be an option.  The code I have will repair the
reference but it doesn't appear to execute when the application is
opened using the runtime executable.  That's the brickwall I'm banging
my head against.

Charlotte Foust

-----Original Message-----
From: Shamil Salakhetdinov [mailto:shamil at smsconsulting.spb.ru] 
Sent: Wednesday, July 16, 2003 8:45 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Broken References in Runtime AXP


Charlotte,

If by "repair a broken reference" you mean its resolving on runtime and
when runtime version of MS Access is used then this should be possbible.
I did that with Access97 using custom profiles:

http://smsconsulting.spb.ru/shamil_s/topics/diffstp.htm
http://smsconsulting.spb.ru/shamil_s/topics/refrefs.htm

The same is still valid for MS Access XP - see its online help's excerpt
in P.S. - RefLibPaths is a the main keyword:

HTH,
Shamil

<snip>