Bob,
Your reply somehow got overlooked, and I just discovered it. Thanks for your
suggestion. I was going to use early binding building the app with Office 97
to make it workable for a prospective client with that version, but I am
wondering if late binding would be best despite a little speed bump. I am not
sure if my app would lose any functionality of later versions with early
binding, but if I recall with late binding it would just pull in the
libraries for whatever version is being used which might be best in my case
as you indicated.
Thanks again, and God bless
Van

"Bob Phillips" wrote:

Use late binding.

Dim oWordApp As Object

Set oWordApp = CreateObject("Word.Application")

etc.

--

HTH

RP

"VanS" wrote in message
...
Hello,
I have an Excel/ Word VBA application using automation. I am trying to
make
it backward compatible to at least Office 2000. My development system has
Office 2003 but the Excel .xls file with MS Office Object Library, MS
Excel
Object Library and MS Word Object Library is on another system with OFfice
2000 in order to bring in the object libraries for that version of
Office(to
make it backward compatible). This latter system is not workable to
develop
on, so the problem is that when I bring the xls file from the Office 2000
into my development box with Office 2003 , the object libraries are
converted
to those for Office 2003, or version 11.

I need to package my app on the newer system, but does anyone know a way
to
retain the older object library versions when I import them into the newer
system?
Thanks, God bless
Van