On May 5, 8:15=A0pm, "Albert D. Kallal" <PleaseNOOOsPAMmkal...@[EMAIL PROTECTED]
>
wrote:
> "Excel 009" <excelmodel...@[EMAIL PROTECTED]
> wrote in message
>
> news:ff33fa17-f52f-4afb-8794-
>
> >Thank you, Albert. =A0I 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? =A0It seems not possible, but the 12.0 objective and Office
> 2003 does coexist on my application. =A0Any 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
thin=
k
> 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 =A0 =A0(Access MVP)
> Edmonton, Alberta Canada
> pleaseNOOSpamKal...@[EMAIL PROTECTED]
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 sup****ting 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
sup****ting 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.
|
