broken references issue

[chrisderoover]

Hello,
I have an Access application that uses some Excel functionality and
therefore lists the Excel object library in its references.
Recently we upgraded some clients to Access 2003, the others are using
Access XP. If I save the db in Access 2003, opening it in Access XP
results in an error.
I understand this is because the Excel 11 object library is not present

on those machines but I cannot found the workaround in code.
If I loop through the references using the .IsBroken property, this
raises an error (err.number 48) for the Excel reference. Because of the

same error I'm not able to remove the reference. In fact I cannot
access any method or property for the faulty reference. And as long as
I don't remove it, Access refuses to load the appropriate Excel 10
reference.
Any suggestions are welcome.
tia
Chris

 

[Douglas J Steele]

Consider using Late Binding, whereby you don't have to set a reference at
all. Tony Toews has some information about this at
http://www.granite.ab.ca/access/latebinding.htm

You might also check what MichKa has at
http://www.trigeminal.com/usenet/usenet026.asp for a possible explanation of
why what you're trying to do isn't working.

 

[chrisderoover]

Thanks for replying Doug. I'll probably switch to late binding. On the
other hand I am still wondering whi I can't use the .isbroken property
on the Excel reference object.
Chris

 

[Douglas J Steele]

As MichKa's article tries to explain, if you don't check quickly enough, the
broken reference might prevent your code from running properly.

 

[chrisderoover]

ok, thanks again Doug.