Microsoft 11.0 vs. 12.0 Object Library

[JK]

I developed an application using Access 2003 SP3. I then tried to deploy it
over a network (split + MDE-FE) when began to experiece a Reference Issue.

On my computer, I only have the MS 12.0 Object Lib available. On at least
one of the user PC's, the MS 11.0 Object Lib is available.

Since the 12.0 was used in the app during development, the end user is
getting a series of errors when they try to log in. In fact, a login attempt
currupts the database.

How should I deal with this situation?

If I run the MS updates on the user PC will the 12.0 Object Library be
available? Or, is there some way to use the 11.0; someway to make it
available on my PC so that I can assign it? If I assign it, will it work on
other user PC's that only have the 12.0 available.

Very Very Very frustratingi situation. It took me a long time to determin
the problem becuase I don't have access to the user's PC and I thought my db
had issues.

Thx!

 

[Allen Browne]

I'm not sure which of these libraries you are are talking about:
- Microsoft Access nn.n Object Library
- Microsoft Office nn.n Object Library

Either way, Access handles these transparently. If you start Access 2007, it
automatically registers and uses the 12.0 libraries. When you start Access
2003, it automatically registers and uses the 11.0 libraries.

It fails to load the right library if:
a) You start another version of Access while you have another one running,
or

b) the user does not have adequate permissions to re-register the library.
For details and solutions, see:
Errors using multiple versions of Access under Vista
at:
http://allenbrowne.com/bug-17.html
The 2nd scenario sounds most likely for your users.

Alternatively, there could be another library you have used that is not
registered on your client's computer. More info about the libraries for each
version of Access:
http://allenbrowne.com/ser-38.html

 

[JK]

That makes a lot of sense. Thank you. I'll research the information you
provided.

Back at my workstation where I only had "Microsoft Office 12.0 Object
Library" available, I did a search in the program files and registered (or
whatever) the 11.0 library.

I think I'm still having issues however.

I'm very confused because at no time did a windows vista machine ever touch
this application. We all have XP 03 & Office 03.

Can I ask you another question? Should I create a specific MDE file for each
user? Or, should I create one MDE file and then create a shortcut to that MDE
file on each users PC?

Thanks!

 

[Allen Browne]

Can I ask you another question? Should I create a specific MDE file for
each
user? Or, should I create one MDE file and then create a shortcut to that
MDE
file on each users PC?

You only need create one MDE, for the lowest version you need to support.
They are backwards compatible only.

For example, if you create an Access 2000 MDE, you can use it in A2002,
2003, or 2007. But if you use Access 2003 to create an Access 2002/3 MDE,
you cannot use it in 2000 nor in 2002.

 

[LarryP]

I'm grappling with this too right now, as our company is "upgrading" to
Office 2007 soon but they consider Access an optional upgrade -- i.e.,
employees can continue using Access 2003 if they like. I just did some
testing of a couple of our databases, and sho nuff, if I move them back and
forth from my 2007 machine to my 2003 machine, the Access and Office
references appear to get reset as appropriate. However, in a couple
databases that interact with Excel and where I have references set to Excel,
that doesn't happen -- once opened on the 2007 machine, back on the 2003
machine they show as missing references. I just mention that FWIW.

 

[Allen Browne]

That's correct, Larry. Access transparently handles the Access nn and Office
nn libraries, but does not automatically alter the libraries of the other
Office applications (Excel, Outlook, Word, ...)

That kinda makes sense, because you hinted that you could have one version
of Excel and a different version of Access on your machine. Therefore Access
should not make the assumption that when you reference Excel 12 but use
Access 11 that you actually want Excel 11.

The solution is to use late binding. Don't include the Excel reference.
Declare as Object rather than Excel app. When the app runs, it will then use
whatever version of Excel is registered on that machine.

More details on late binding:
http://www.granite.ab.ca/access/latebinding.htm
http://support.microsoft.com/kb/210111
http://support.microsoft.com/kb/260410

 

[LarryP]

Thanks very much, Allen, that's a bit of knowledge I'll definitely put to
use. I've read other "late binding" threads, but until now it has always
been kinda like listening to two guys talk about quantum physics. This
connects it to something that's real for me. Bye for now, got some databases
to modify!

 

[Tony Toews [MVP]]

Back at my workstation where I only had "Microsoft Office 12.0 Object
Library" available,

Why do you have a reference set to that object library? The MS Access
Object library sure. But the MS Office library? That's rather
unusual.

If you think you might not be using it remove it and recompile the
project and see if any errors occur.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Tony Toews [MVP]]

I developed an application using Access 2003 SP3. I then tried to deploy it
over a network (split + MDE-FE) when began to experiece a Reference Issue.

What references do you have?

Sub DebugPrintReferences()

Dim ref As Reference

For Each ref In Access.References
Debug.Print ref.Name & " " & _
IIf(ref.IsBroken, "Broken", _
ref.Major & "." & ref.Minor & " " & _
ref.FullPath)
Next ref

End Sub

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/