Missing references to Office 11

[Andrew]

Hi all

I'm developing a database for a client in Access 2003. (The database,
not the client. He's in London )

Had a load of problems with Access this morning, in that every time I
tried to open the database, it generated loads of errors, tried to
copy the objects into a new database, equally many errors, then tried
to create another new database and check the references in the VBA
window and even though there was no data and no objects this caused a
crash....

So, having rebooted with no imrpovement in performance, I decided to
remove and reinstall Office 2003. My machine already has Office 2007,
and I did a full install of everything (except Outlook 2003).

Rebooted again and completed the downloads of SPs etc, rebooted again.

Now when I create a database and in the VBA editor go to Tools -->
References, there is no available reference to the Microsoft Office
11.0 object library. Office 12 is there, but no Office 11. My client
uses Office 2003, and this is crucial to me - does anyone know how I
can restore these references?

Thanks a lot

Andrew

 

[Douglas J. Steele]

Try clicking on the Browse button in the References dialog, and pointing to

C:\Program Files\Common Files\Microsoft Shared\OFFICE11\MSO.DLL

 

[George Nicholson]

Also, if you have the Office 2007 Compatibility pack installed (which you
might have done to use 2007 files with 2003 before you installed 2007), you
might consider uninstalling it. It seems to automatically change the MSO
reference in Access 2003 (and 2002, I assume) from 11 to 12.

My experience: using 2003 with 2007 Compatibility pack, I sent a 2003 mdb to
client (with straight 2003) that they couldn't open without errors. Once I
uninstalled the compatibility pack on my machine the MSO reference changed
from 12 to 11. I resent the file and the client had no problem.

Another workaround might be to have the client install the free Office 2007
compatibilty pack.

 

[Tony Toews [MVP]]

Now when I create a database and in the VBA editor go to Tools -->
References, there is no available reference to the Microsoft Office
11.0 object library. Office 12 is there, but no Office 11. My client
uses Office 2003, and this is crucial to me - does anyone know how I
can restore these references?

Why do you need the reference to MS Office object in the first place?
Can it be removed?

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/

 

[David W. Fenton]

:

Now when I create a database and in the VBA editor go to Tools -->
References, there is no available reference to the Microsoft
Office 11.0 object library. Office 12 is there, but no Office 11.
My client uses Office 2003, and this is crucial to me - does
anyone know how I can restore these references?

Have you just tried deleting the reference and seeing if the app
compiles? I have never used anything from that library, so always
remove it from references myself.

 

[aaron.kempf]

warning

this is really t o n y t o e w s

You _DEFINITELY_ shouldn't listen to him because he doesn't know the
pros and cons of any real database systems

god damn kid playing in the sandbox.... when are you going to hit the
1gb limit?
and he stalks me.

He's a stupid canuck!

 

[Andrew]

Have you just tried deleting the reference and seeing if the app
compiles? I have never used anything from that library, so always
remove it from references myself.

Hi

Yes, I've tried without it, but get errors because in various places
I've used the FileDialog object to display the File picker dialog box.

Is there another way around this without using late binding?

Thanks, Doug, incidentally, for the location of the file. Never done
this, but presumably I could use Application.References.AddFromFile as
long as the clients will all have the file available?

Thanks
Andrew

 

[Douglas J. Steele]

Yes, I've tried without it, but get errors because in various places
I've used the FileDialog object to display the File picker dialog box.

Is there another way around this without using late binding?

If all you're doing is using the File picker dialog box, do yourself a huge
favour and scrap it.

Instead, use the all-API approach demonstrated in
http://www.mvps.org/access/api/api0001.htm at "The Access Web". Far more
reliable.

Thanks, Doug, incidentally, for the location of the file. Never done
this, but presumably I could use Application.References.AddFromFile as
long as the clients will all have the file available?

Theoretically, you could, but I wouldn't recommend it (since, as I said
above, you don't need it.)

Incidentally, what's your objection to late binding? I'd say that's always
the best approach to take: you want to have the minimum number of references
that you can.

 

[aaron_kempf]

Warning

David Fenton makes inaccurate and incorrect statements.

I would reccomend finding a certified SQL Server DBA or Developer in
order to fit your database needs.

This 'D A V I D F E N T O N' kid learned his databases on the back of
a cracker jacks box

-Aaron Kempf
MCITP: DBA