Microsoft office 12.0 object library for Access 2003

[Excel 009]

Hi,

In my office I have Office 2003 on the PC. I created an Access
application which has a component reference to Microsoft Office 12.0
Object Library.

The problem that I am having now it that in my home PC I also have
Office 2003, but I only have Microsoft Office 11.0 Object Library in
it and not Microsoft Office 12.0 Object Library, so the application
does not work right.

I read info from the Internet and found out that the Microsoft Office
12.0 Object Library is for Office 2007.

How can I have Microsoft Office 12.0 Object Library on my Office 2003
PC and be able to call it in my Access 2003 application?

Excel 009

[Albert D. Kallal]

You don't mention what computing your using, but if its part of office 2007,
then you going to have a copy of office 2007.

Are you really sure you need this reference?

I for the most part tend to removed MOST of the references (outlook, excel
etc), and use late binding to ensure the application functions....

It just no clear what/why you needed this reference in the first place...

How can I have Microsoft Office 12.0 Object Library on my Office 2003
PC and be able to call it in my Access 2003 application?

If you really do need that reference, then you simply have no choice, and
you will need to have office 2007 installed on that pc...

I just trying to make sure you actually need that reference...

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com

[Excel 009]

On May 4, 6:28*pm, "Albert D. Kallal" <[e-mail]>
wrote:

You don't mention what computing your using, but if its part of office 2007,
then you going to have a copy of office 2007.

Are you really sure you need this reference?

I for the most part tend to removed MOST of the references (outlook, excel
etc), and use late binding to ensure the application functions....

It just no clear what/why you needed this reference in the first place...

*How can I have Microsoft Office 12.0 Object Library on my Office 2003

PC and be able to call it in my Access 2003 application?

If you really do need that reference, then you simply have no choice, and
you will need to have office 2007 installed on that pc...

I just trying to make sure you actually need that reference...

--
Albert D. Kallal * *(Access MVP)
Edmonton, Alberta Canada
[e-mail]

Thank you, Albert. I am not quite sure if I need the 12.0 object or
not, but assume I need it, how can I install it on a PC only with
Office 2003? It seems not possible, but the 12.0 objective and Office
2003 does coexist on my application. Any idea?

Excel 009

[Albert D. Kallal]

"Excel 009" <ex***********@gmail.comwrote in message
news:ff33fa17-f52f-4afb-8794-

>Thank you, Albert. I am not quite sure if I need the 12.0 object or

not, but assume I need it, how can I install it on a PC only with
Office 2003? It seems not possible, but the 12.0 objective and Office
2003 does coexist on my application. Any idea?

Excel 009

----------

Good, if you don't know if you need it, then that reference was likely put
in by accident. I would simply remove the reference, and then do a
debug-compile to see if the code runs an compiles (and, alternatively put
office 11 reference to see if that fix..).

You are MUCH better off to see if things work without the reference then
trying to mix and match references in your software straddled between two
versions of office. You REALLY want to make efforts to avoid that kind of
train wreck, and the resulting nightmares of support problems that will
incur if you do in fact need both references. Really, just don't even think
of going down this road if it can be avoided.

It would mean that every time you need that software installed, you going to
have to install two versions of office to make it function. Your goal here
is remove that reference if possible. I don't know of ANYONE deploying
access applications that require two different office library references. It
just not done, and is not a supportable nor reliable setup.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com

[Jane]

On May 5, 8:15*pm, "Albert D. Kallal" <[e-mail]>
wrote:

"Excel 009" <[e-mail] in message

news:ff33fa17-f52f-4afb-8794-

Thank you, Albert. *I am not quite sure if I need the 12.0 object or

not, but assume I need it, how can I install it on a PC only with
Office 2003? *It seems not possible, but the 12.0 objective and Office
2003 does coexist on my application. *Any idea?

Excel 009

----------

Good, if you don't know if you need it, then that reference was likely put
in by accident. I would simply remove the reference, and then do a
debug-compile to see if the code runs an compiles (and, alternatively put
office 11 reference to see if that fix..).

You are MUCH better off to see if things work without the reference then
trying to mix and match references in your software straddled between two
versions of office. You REALLY want to make efforts to avoid that kind of
train wreck, and the resulting nightmares of support problems that will
incur if you do in fact need both references. Really, just don't even think
of going down this road if it can be avoided.

It would mean that every time you need that software installed, you going to
have to install two versions of office to make it function. Your goal here
is remove that reference if possible. I don't know of ANYONE deploying
access applications that require two different office library references. It
just not done, and is not a supportable nor reliable setup.

--
Albert D. Kallal * *(Access MVP)
Edmonton, Alberta Canada
[e-mail]

Well, I hate to say it, but my department is in this very
predicament. I have a database system that unfortunately someone
higher than me offered to "share" with another division. The only
problem is, nobody asked me my opinion and I'm stuck supporting this
monster. This works great when it's in an environment where I have
some control over upgrades, etc.. But when I'm dealing with
supporting an application in which "we" have to deal with a division
that is on it's own upgrade schedule, then it becomes a nightmare.

Case in point. My department is using Windows XP (we aren't touching
Vista with a 10' pole until somebody drags us there kicking and
screaming) with Office 2007. Only problem is the division that is
sharing is using Office 2003. Fortunately, we aren't using the same
MDE. I make a MDE for us using Office 2007 and an MDE from a
machine with Office 2003 for them on a different server volume. This
is more work for us, but it does work.

Unfortunately, we have to use the Outlook library because I have
mailing code for all sorts of processes (automatic mailers based off
of specific actions...confirmation mailings, error messages sent to
the IT group if somebody encounters an error in specific processes,
several large mailings that are set up on an automation schedule).

I can't WAIT to get them off of this. My recommendation is don't use
a mixed environment if you can at ALL help it. It's a real
headache.

[Albert D. Kallal]

"Jane" <al********@missouri.eduwrote in message
news:f66bf07e-f556-4875-9791-

>Unfortunately, we have to use the Outlook library because I have

mailing code for all sorts of processes
sure, then use late binding, and it will just fine.

There's not a competent developer in the last ten years in this newsgroup
that has ever suggested to use early binding in this case.

If you use late binding in your code, you can use different versions of
outlook for your application, and it will work fine.

I have a super easy mail merge sample download that thousands of people in
this newsgroup have used for years, and they've used it with every
conceivable version of access and every conceivable version of word, and
they've NEVER had one problem or one breakage and almost ten years of usage.

It is a mount Everest, humongous, large, massive different issue you are
experiencing than the original poster. The original poster was using two
references to two different office libraries at the SAME TIME, and you are
not attempting to do anything and nearly remotely close to this.

If you simply want a use outlook automation code, you can do so with every
conceivable version of outlook and your code will not break, and you do NOT
need a reference to the outlook library to do so.

You need to use late binding, it is explained here:
http://www.granite.ab.ca/access/latebinding.htm
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com

[Tony Toews [MVP]]

"Albert D. Kallal" <Pl*******************@msn.comwrote:

>sure, then use late binding, and it will just fine.

As Albert knows but didn't mention late binding also works for Excel, Word and other
such.

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/