VB.NET Desktop Application Built on Windows XP, Excel 2003

[snare88]

I have a question regarding a VB.NET 2003 application which was built
on a Windows XP machine with Office 2002 installed. The software does
some interfacing with Microsoft Excel. I now want to run this
application on a Windows 2000 machine with Office 2003 installed.
However, it is not functioning correctly. The application DOES work
on a Windows XP machine running Office 2003. I am referencing the
"Microsoft Excel 10.0 Object Library". I find it strange that this
app works with some Office 2003 machines while not on others. Is
there a compatibility issue with Windows 2000 and Excel 2003
combination? Am I missing something else?

Any help would be greatly appreciated.

Thanks
dave

[RobinS]

<sn*****@gmail.comwrote in message
news:11**********************@q2g2000cwa.googlegro ups.com...

>I have a question regarding a VB.NET 2003 application which was built
on a Windows XP machine with Office 2002 installed. The software does
some interfacing with Microsoft Excel. I now want to run this
application on a Windows 2000 machine with Office 2003 installed.
However, it is not functioning correctly. The application DOES work
on a Windows XP machine running Office 2003. I am referencing the
"Microsoft Excel 10.0 Object Library". I find it strange that this
app works with some Office 2003 machines while not on others. Is
there a compatibility issue with Windows 2000 and Excel 2003
combination? Am I missing something else?

Any help would be greatly appreciated.

Thanks
dave

What do you mean, it works on some machines while not on others? What does
it do that indicates it's not working?

Robin S.

[susiedba]

I would reccomend:

a) using VBA for Excel automation
b) not planning on deploying 'framework apps' onto desktops
- it isn't on any desktops
- it's impossible to even determine which desktops have which
version

it's like.. the person who designed the grand .NET strategy had 'never
taken a tech support call in their life'

there is literally NO predictable way to even determine 'which version
of the framework lives on which machine' that will work for every
version of Windows

On Feb 23, 11:18 am, "RobinS" <[e-mail]:

<[e-mail] in message

news:11**********************@q2g2000cwa.googlegro ups.com...

I have a question regarding a VB.NET 2003 application which was built
on a Windows XP machine with Office 2002 installed. The software does
some interfacing with Microsoft Excel. I now want to run this
application on a Windows 2000 machine with Office 2003 installed.
However, it is not functioning correctly. The application DOES work
on a Windows XP machine running Office 2003. I am referencing the
"Microsoft Excel 10.0 Object Library". I find it strange that this
app works with some Office 2003 machines while not on others. Is
there a compatibility issue with Windows 2000 and Excel 2003
combination? Am I missing something else?

Any help would be greatly appreciated.

Thanks
dave

What do you mean, it works on some machines while not on others? What does
it do that indicates it's not working?

Robin S.

[vovan]

My VB6 application worked fine on Windows 2000 until SP4 was installed. With
SP 4 it started to crash at the beginning. I've heard from somebody that SP
for Windows 2000 had a lot of bugs.
Maybe some of your 2000 machines have SP4, some don't

Just my 2 cents
vovan

"RobinS" <Ro****@NoSpam.yah.nonewrote in message
news:CJ******************************@comcast.com. ..

>
<sn*****@gmail.comwrote in message
news:11**********************@q2g2000cwa.googlegro ups.com...

>>I have a question regarding a VB.NET 2003 application which was built
on a Windows XP machine with Office 2002 installed. The software does
some interfacing with Microsoft Excel. I now want to run this
application on a Windows 2000 machine with Office 2003 installed.
However, it is not functioning correctly. The application DOES work
on a Windows XP machine running Office 2003. I am referencing the
"Microsoft Excel 10.0 Object Library". I find it strange that this
app works with some Office 2003 machines while not on others. Is
there a compatibility issue with Windows 2000 and Excel 2003
combination? Am I missing something else?

Any help would be greatly appreciated.

Thanks
dave

What do you mean, it works on some machines while not on others? What does
it do that indicates it's not working?

Robin S.

[susiedba]

you probably don't know how to keep your machines free of spyware.

it's not rocket science; you just have to follow industry 'best
practices'

I do follow best practices; but Visual Studio.NET still runs like crap

On Feb 23, 1:28 pm, "vovan" <[e-mail]:

My VB6 application worked fine on Windows 2000 until SP4 was installed. With
SP 4 it started to crash at the beginning. I've heard from somebody that SP
for Windows 2000 had a lot of bugs.
Maybe some of your 2000 machines have SP4, some don't

Just my 2 cents
vovan

"RobinS" <[e-mail] in message

news:CJ******************************@comcast.com. ..

<[e-mail] in message
news:11**********************@q2g2000cwa.googlegro ups.com...

>I have a question regarding a VB.NET 2003 application which was built
on a Windows XP machine with Office 2002 installed. The software does
some interfacing with Microsoft Excel. I now want to run this
application on a Windows 2000 machine with Office 2003 installed.
However, it is not functioning correctly. The application DOES work
on a Windows XP machine running Office 2003. I am referencing the
"Microsoft Excel 10.0 Object Library". I find it strange that this
app works with some Office 2003 machines while not on others. Is
there a compatibility issue with Windows 2000 and Excel 2003
combination? Am I missing something else?

Any help would be greatly appreciated.

Thanks
dave

What do you mean, it works on some machines while not on others? What does
it do that indicates it's not working?

Robin S.