[AccessD] References (again) - Access 97

Hi Greg

Charlotte is right. If you feel you have a need to fiddle with the
references, this is the very first thing to do. No exceptions.

Also, doing so will leave your app decompiled and you may need to
recompile afterwards.

We had a long thread on this topic.
Look up the archive on

  "Broken References in Runtime AXP and A97"

of 2003-07-23.

/gustav


> Greg,

> It is logical that you cannot declare any objects before you verify the
> references.  Even if the Office library isn't the one that's broken, you
> need to test the references before you do *anything* else, including
> declare object variables as anything but Object.

> Charlotte Foust


> -----Original Message-----
> From: Greg Smith [mailto:GregSmith at starband.net] 
> Sent: Thursday, August 05, 2004 6:58 AM
> To: accessd at databaseadvisors.com
> Subject: [AccessD] References (again) - Access 97


> Hi everyone...

> Thanks to everyone who responded to my earlier post(s) about references
> and how to find broken ones (I don't have my list here at work so I
> don't have all the responses).

> I still have the references issue.  And it may be because of how I'm
> starting the program or how I have the references set.  There is only
> one right now that is giving me the PITA, and it's to mso97.dll in the
> Office directory.  Hard to test that one too, because if you delete it,
> Access won't start.

> I can use the References.AddFromFile(...) code to set the reference.
> But there's a catch-22...if I don't have a reference to the MS Office
> 8.0 Object library, then the code:

> Dim cbr as CommandBar

> fails just before I can set the reference using:

> SetRef = References.AddFromFile("c:\program
> files\msoffice97\office\mso97.dll")