DH QBF

[Secret Squirrel]

I also have Excel 2003. When I look at the references on my db using access
2003 I see the Excel 11.0 and the Access 11.0. On 2000 they are both 9.0. And
everything works fine using 2000. But it won't work correctly using 2003. Is
there a way to find out if these references are causing the problem and is
there a way to correct it?

 

[Secret Squirrel]

You think this will solve the problem and have it work on both versions of
access?

 

[Van T. Dinh]

Uncheck "Microsoft ActiveX Data Objects 2.1 Library" and select one of later
version (the latest is 2.8 so 2.1 is REALLY out of date). If you don't have
any later version on both the laptop & desktop, you need to patch the OS and
Access.

 

[Douglas J. Steele]

As I said, Access 2003 should correctly translate the Access 9.0 reference,
but it may not correct the Excel 9.0 reference.

Assuming you're actually using Excel in your code, there are 2 ways to
determine whether the reference to Excel 9.0 is a problem. Replace the
reference with a reference to Excel 11.0, or remove the reference completely
and use Late Binding. Even though I know all of the desktops in my company
have the same version of Excel, I always use Late Binding so that I know I
won't have a problem when we move to another version of Excel.

 

[Secret Squirrel]

But what if the code that is erroring out has nothing to do with Excel. Will
is still cause problems?

 

[Douglas J. Steele]

Yes. References are like apples: one bad one can spoil the whole bunch.
Anytime Access has to go out searching for a function that's contained in
one of the referenced files, a broken reference can cause problems. It's
extremely common for VBA functions such as Left and Format to break, even
though the broken reference is seldom the one that contains those functions.

 

[Secret Squirrel]

Well in my 2003 there is no reference excel 9.0. It only has 11.0. I wonder
if that could be causing the problem. Is there anyway to use or add 9.0 since
it seems to work fine with that one?

 

[Van T. Dinh]

Don't know but you should ALWAYS use the lastest version. Generally, if
Microsoft put out a newer version, it is for the purpose of fixing some
bugs. I rather use a fixed version rather than a bugsy version whether the
bugs affect my application. As you have learnt, some bugs are extremely
hard to find so why take the unnecessary risks?

 

[Douglas J. Steele]

If you've only got Excel 2003 on the machine, you MUST use the Excel 11.0
reference.

 

[Secret Squirrel]

Well the problem is that I have 2000 on my pcs at work and there it no plan

 

[Van T. Dinh]

ADO is available as a free upgrade to 2.8 regardless whether you have Access
2000 or Access 2003.

OTOH, IIRC, you wrote before that you copied the data to your laptop and it
worked in A2000 on your laptop then use this copy at work.