"Excel 009" <excelmodeling@[EMAIL PROTECTED]
> wrote 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 sup****t 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 sup****table nor reliable setup.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@[EMAIL PROTECTED]
|
