Windows'XP/Office'97 incompatibility

[Tom Edelbrok]

PROBLEM: We are upgrading users to Windows XP from NTWS 4.0, but are leaving
them running Office 97 (because we haven't purchased any licenses for Office
upgrades). This causes a serious problem with our VB 6.0 programs that
attempt to create Excel objects. They now give error "-2147417851" when
trying to do a "Workbooks.Add".

This problem seems to affect only the Windows XP / Office 97 combination,
because NTWS 4.0 / Office 97 works fine when creating Excel objects.
Furthermore, installing an Office 2000 upgrading fixes the problem.

Because our site isn't going to purchase Office upgrades how can we get
around this problem? Applying an Office 2000 upgrade fixes it, but we aren't
permitted to go that way. Is there any other solution?

Thanks in advance,

Tom Edelbrok

 

[Miss Perspicacia Tick]

PROBLEM: We are upgrading users to Windows XP from NTWS 4.0, but are
leaving them running Office 97 (because we haven't purchased any
licenses for Office upgrades). This causes a serious problem with our
VB 6.0 programs that attempt to create Excel objects. They now give
error "-2147417851" when trying to do a "Workbooks.Add".

This problem seems to affect only the Windows XP / Office 97
combination, because NTWS 4.0 / Office 97 works fine when creating
Excel objects. Furthermore, installing an Office 2000 upgrading fixes
the problem.
Because our site isn't going to purchase Office upgrades how can we
get around this problem? Applying an Office 2000 upgrade fixes it,
but we aren't permitted to go that way. Is there any other solution?

Thanks in advance,

Tom Edelbrok

Please do not multipost.

 

[Miss Perspicacia Tick]

PROBLEM: We are upgrading users to Windows XP from NTWS 4.0, but are
leaving them running Office 97 (because we haven't purchased any
licenses for Office upgrades). This causes a serious problem with our
VB 6.0 programs that attempt to create Excel objects. They now give
error "-2147417851" when trying to do a "Workbooks.Add".

This problem seems to affect only the Windows XP / Office 97
combination, because NTWS 4.0 / Office 97 works fine when creating
Excel objects. Furthermore, installing an Office 2000 upgrading fixes
the problem.
Because our site isn't going to purchase Office upgrades how can we
get around this problem? Applying an Office 2000 upgrade fixes it,
but we aren't permitted to go that way. Is there any other solution?

Thanks in advance,

Tom Edelbrok

Please do not multipost.

 

[Miss Perspicacia Tick]

PROBLEM: We are upgrading users to Windows XP from NTWS 4.0, but are
leaving them running Office 97 (because we haven't purchased any
licenses for Office upgrades). This causes a serious problem with our
VB 6.0 programs that attempt to create Excel objects. They now give
error "-2147417851" when trying to do a "Workbooks.Add".

This problem seems to affect only the Windows XP / Office 97
combination, because NTWS 4.0 / Office 97 works fine when creating
Excel objects. Furthermore, installing an Office 2000 upgrading fixes
the problem.
Because our site isn't going to purchase Office upgrades how can we
get around this problem? Applying an Office 2000 upgrade fixes it,
but we aren't permitted to go that way. Is there any other solution?

Thanks in advance,

Tom Edelbrok

Please do not multipost.

 

[Miss Perspicacia Tick]

PROBLEM: We are upgrading users to Windows XP from NTWS 4.0, but are
leaving them running Office 97 (because we haven't purchased any
licenses for Office upgrades). This causes a serious problem with our
VB 6.0 programs that attempt to create Excel objects. They now give
error "-2147417851" when trying to do a "Workbooks.Add".

This problem seems to affect only the Windows XP / Office 97
combination, because NTWS 4.0 / Office 97 works fine when creating
Excel objects. Furthermore, installing an Office 2000 upgrading fixes
the problem.
Because our site isn't going to purchase Office upgrades how can we
get around this problem? Applying an Office 2000 upgrade fixes it,
but we aren't permitted to go that way. Is there any other solution?

Thanks in advance,

Tom Edelbrok

Please do not multipost.

 

[Miss Perspicacia Tick]

PROBLEM: We are upgrading users to Windows XP from NTWS 4.0, but are
leaving them running Office 97 (because we haven't purchased any
licenses for Office upgrades). This causes a serious problem with our
VB 6.0 programs that attempt to create Excel objects. They now give
error "-2147417851" when trying to do a "Workbooks.Add".

This problem seems to affect only the Windows XP / Office 97
combination, because NTWS 4.0 / Office 97 works fine when creating
Excel objects. Furthermore, installing an Office 2000 upgrading fixes
the problem.
Because our site isn't going to purchase Office upgrades how can we
get around this problem? Applying an Office 2000 upgrade fixes it,
but we aren't permitted to go that way. Is there any other solution?

Thanks in advance,

Tom Edelbrok

Please do not multipost.

 

[Miss Perspicacia Tick]

PROBLEM: We are upgrading users to Windows XP from NTWS 4.0, but are
leaving them running Office 97 (because we haven't purchased any
licenses for Office upgrades). This causes a serious problem with our
VB 6.0 programs that attempt to create Excel objects. They now give
error "-2147417851" when trying to do a "Workbooks.Add".

This problem seems to affect only the Windows XP / Office 97
combination, because NTWS 4.0 / Office 97 works fine when creating
Excel objects. Furthermore, installing an Office 2000 upgrading fixes
the problem.
Because our site isn't going to purchase Office upgrades how can we
get around this problem? Applying an Office 2000 upgrade fixes it,
but we aren't permitted to go that way. Is there any other solution?

Thanks in advance,

Tom Edelbrok

Please do not multipost.

 

[Miss Perspicacia Tick]

PROBLEM: We are upgrading users to Windows XP from NTWS 4.0, but are
leaving them running Office 97 (because we haven't purchased any
licenses for Office upgrades). This causes a serious problem with our
VB 6.0 programs that attempt to create Excel objects. They now give
error "-2147417851" when trying to do a "Workbooks.Add".

This problem seems to affect only the Windows XP / Office 97
combination, because NTWS 4.0 / Office 97 works fine when creating
Excel objects. Furthermore, installing an Office 2000 upgrading fixes
the problem.
Because our site isn't going to purchase Office upgrades how can we
get around this problem? Applying an Office 2000 upgrade fixes it,
but we aren't permitted to go that way. Is there any other solution?

Thanks in advance,

Tom Edelbrok

Please do not multipost.

 

[Miss Perspicacia Tick]

PROBLEM: We are upgrading users to Windows XP from NTWS 4.0, but are
leaving them running Office 97 (because we haven't purchased any
licenses for Office upgrades). This causes a serious problem with our
VB 6.0 programs that attempt to create Excel objects. They now give
error "-2147417851" when trying to do a "Workbooks.Add".

This problem seems to affect only the Windows XP / Office 97
combination, because NTWS 4.0 / Office 97 works fine when creating
Excel objects. Furthermore, installing an Office 2000 upgrading fixes
the problem.
Because our site isn't going to purchase Office upgrades how can we
get around this problem? Applying an Office 2000 upgrade fixes it,
but we aren't permitted to go that way. Is there any other solution?

Thanks in advance,

Tom Edelbrok

Please do not multipost.

 

[Miss Perspicacia Tick]

PROBLEM: We are upgrading users to Windows XP from NTWS 4.0, but are
leaving them running Office 97 (because we haven't purchased any
licenses for Office upgrades). This causes a serious problem with our
VB 6.0 programs that attempt to create Excel objects. They now give
error "-2147417851" when trying to do a "Workbooks.Add".

This problem seems to affect only the Windows XP / Office 97
combination, because NTWS 4.0 / Office 97 works fine when creating
Excel objects. Furthermore, installing an Office 2000 upgrading fixes
the problem.
Because our site isn't going to purchase Office upgrades how can we
get around this problem? Applying an Office 2000 upgrade fixes it,
but we aren't permitted to go that way. Is there any other solution?

Thanks in advance,

Tom Edelbrok

Please do not multipost.