[AccessD] Broken References

Hi Andy

Refer to the oldest version.
That may not work, though. If so, you will have to deal with it actively. Look up and study the old threads on the subject:

2006-09: DAO References in New DBs
2006-08: Removing a missing reference
2006-07: Set references programmatically
2004-08: Test for a Particular Reference in Code
2003-07: Broken References in Runtime AXP and A97. Solved!
2002-02: Checking References in Code
2001-09: Set References through Code
2001-07: Conditional reference

The general trick is to remove _a_ reference and add it back. Then recompile, which is true challenge as this is not as easy as it sounds, because running code cannot compile itself.

Another option is to use late binding. It's a bit slower and won't allow for IntelliSense during development, though a trick to avoid this is to reference the library when writing code, then remove the reference and revert to late binding. This topic has been discussed many times through the years.

/gustav

>>> andy at minstersystems.co.uk 20-11-2008 00:00 >>>
Hi folks

If you have 2 machines with different versions of Office, and your app needs
a reference to Excel, how do you achieve that without errors? I kind of
stumble through this when I get it but I've never fully understood.
Sometimes it seems that if I compile on pc1 and copy to pc2 the app
recompiles when you start the app, whereas in other situations it seems to
error. Is it anything to do with which way you're doing it - eg if you
compile on a pc with, say, Office 2000 and then move the app to where
there's Office XP that's ok, but the reverse fails. Anything like that?
Anyone know the rule?

I'm headed for bed so I'll look forward to your pearls of wisdom when I
crawl out of the sack.

Cheers

Andy Lacey