Reference Object library 10.0?

Can you not simply replace the MSACC11.OLB file in your office directory with MSACC10.OLB. You might have a few compile issues at first, but you could work them out as you go. Just a thought.
J

J - thanks for the suggestion.  The main object library I am having a problem with is the Excel Object Library 11.  My client only has Excel Object 10 so the reference comes across as missing.

The only file I saw in my directory is MSACC.OLB.  I don't see a MSACC11.OLB.

Sorry Mage,
didn't know it was Excel...
I'm using C:\Program files\Microsoft Office\Office\EXCEL9.OLB for my 2000 database. Maybe you have something similar?

No I have don't have that in the office folder.  I have 3 folders in Microsoft Office\

1.) Office
2.) Office10
3.) Office11

Office and Office10 don't have any Excel.OLB files.  Neither does Office11.  The Excel reference is linked to Excel.exe

Hi Mage,
When you open your database VBA and look at the references , when you highlight the excel Item, Does it give you the location of the 11 Object?

It does give me the location of the 11 object in my Access 2003 copy.  It doesn't give me the location in the Access XP version.

Location is C:\Program Files\Microsoft Office\OFFICE11\Excel.exe

rockiroads - Thanks for the link, I will try out the code tonight and let you know how it works out.

Danny - good link and I fully agree.  I informed my client that I had a different version of Office and they would have to install or pay for the version of Office for my computer.  They declined so now we run into these types of issues.

The contract is a very small contract (under $500) and I would lose money if I went and purchased the software myself.  They were well aware of these issues ahead of time but now they have experienced it and they have blood in their eyes.  

Ya gotta love it....<sigh>  Needless to say, this is the last contract I do with this company.

I am giving them the .mdb file and they are compiling the mdb on there side but that is when the problem occurs.

For now I am having them manually change the references from 11.0 to 10.0 but they are unhappy with that solution.  if rockiroads solution does not work then I'll tell them they have to make those changes until they upgrade to office 2003.

What you could do is have them advise you of the locations for their dll/ocx files for references.
You then recreate the file locations on your machine, compile and that should do you...

:-)

I have this same problem Mage, I develop on an XP machine, and most of the rest of the company is still on 2000, some older. so I actually have a dinosaur sitting on my desk that I dedicated solely to compiling with an older version. Not the best way to do business....but necessity is the mother....and all that.  :o)
J

I develop in 2003 (2000 default) predominantly, and have a seperate machine with A97 (just in case).
I'm off to a MS roadshow next week on Office12 and they tend to give out software, so I might have yet another machine (Vista and Office12)...

Generally, when I ask clients what version they have, I always advise against A2002 (mainly cos it's sh!te - least stable of all releases).
If they say A97, then I do the "it's been out for 11 years - time to upgrade" routine.

Ps: forgot to mention article "Dealing with References-Overview" in second link.

great links!  I'll check these all out and distribute some points either tomorrow or Sunday :)

Mage, the link I gave contains code that refreshes links. Its supposed to emulate you unselecting MISSIN references then checking it again. This code is from MS. I got it ages ago but I dont have the link anymore. U could try searching in msdn.microsoft.com
or microsoft's support site
for full details of the code

Yes, it looks like it is what I will need.  I am eagerly awaiting testing out your code tonight to see what happens.  I'll keep you posted!

both rockiroads and puppydog led me in the directly I needed to go.  Thanks for everyone's input!