The first trick in broken refs to make sure that you REMOVE any possible
reference you don't need.
So, any reference to outlook, excel, word etc. needs to be removed. You need
to use late binding..
Either setup a test mule box, or even better setup a virtual pc. You need to
be able to test a install, then wipe that install complete free as if your
install never happened...so you can test again and again. Either setup a
Norton ghost (the old way), or get your hands on virtual pc.
The Microsoft team has 80 FULL TIME people just to work on, and setup the
install for JUST excel.
My point here is that you really need to put together some SERIOUS resources
here to test your deployment of your application. If you don't, you will
spend MORE on support and troubleshoots then the cost of your software!!!
So, broken refs needs to be checked first....
Allen Browne
http://allenbrowne.com/ser-38.html
Doug Steele:
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html
Peter Walker:
http://www.papwalker.com/dllhell/index-page2.html
MsKb Articles: 310803, 208218, 209849, 286300
ACC2000: How Access 2000 Resolves Visual Basic for Applications References
http://support.microsoft.com/default.aspx?scid=kb;en-us;248941
ACC2000: How to Resolve Reference Issues in an Access Database
http://support.microsoft.com/default.aspx?scid=kb;en-us;310803