Newer references on older versions of Access!! 1

[JennyPeters]

I am creating Access Projects in Access 2002, which use the Excel 10.0 Object library. But, when deploying the application on Access 2000 machines, they don't have this reference, and hence an error occurs.

The 10.0 refernce can't be registered on a 2000 office machine without problems.

So, how can I deal with this situation?

Jenny Peters

 

[randysmid]

Hi Jenny,
I am having the same trouble, but with Access 2000 running on my users' machines (which are Win2K). Whenever I try to make changes or enhancements from my WinXPPro machine, I end up introducing errors because of the references. So, I am forced to do my updates on someone else's Win2K machine until we are all on the same page.

HTH,
Randy Smith, MCP
rsmith@cta.org
California Teachers Association

 

[PHV]

You may use late binding, i.e. only play with non typed Objects, something like this:
Dim objXL As Object
Set objXL = CreateObject("Excel.Application")
You can then remove the reference to Excel x.0 Object Library

Hope This Help, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[vbajock]

I called MS on this one. Of course, they said the solution was to "upgrade your software". I haven't found any other solution other than maintaining different versions for different machines.

 

[psemianonymous]

PHV has the standard answer. Use late binding to open any (reasonably recent) version of Excel, and user#1 can be using a different version of Excel from user#2 and developer#1 (that's you).

You can search comp.databases.ms-access for some examples. There are plenty. (see link below)


Pete

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[JennyPeters]

I wasn't aware that you could do that, so I am quite excited about trying it.

I will post my findings!

Thanks,

Jenny