Gruff

I created a VB 2010 standard edition App on Windows 7 that behaves badly when installed on WinXP.

This same app works properly when installed on Windows 7.

On WinXP it runs and all functions (So far) work except one
A button click is suppose to launch a backgroundworker that queries a database and displays the data in a datagridview. I am using the background worker so that a progress bar can be shown.

On the button click the progress bar runs for a bit then stops and no data is displayed. It is like the background worker failed.

The odd thing is that a similar function launched with another button works fine.
Both run queries in the background worker.

Without errors I am at a loss.

Any suggestions?

Schravendeel

Can you try installing Visual studio 2010 on the xp computer and run the program through the debugger? Does that give you any errors? (Be sure to remove any Try-Catch blocks in your code)

Gruff

I have 2010 express on the XP machine but I do not think it will let me load the Window 7 VB project as it is the full version of VB.NET 2010 Standard Edition.

I only have one license for the latter.

Good idea about the try-Catch. I'll pursue that course for now.

AtmaWeapon

Make sure you aren't eating the exception (you're already on that.) Also make sure you're looking for the exception. When the BackgroundWorker finishes and raises the RunWorkerCompleted event, check the Error property of the RunWorkerCompletedEventArgs. If OnDoWork() failed with an exception, this property should contain the exception (unless you handled it in OnDoWork().)

Gruff

Thanks Atma, I added the check for the error property in completed this morning but haven't compiled and tested. Got carried away redesigning the whole query chain.

Gruff

I didn't trap an error with the code this morning so I re-designed and re-wrote the whole query chain of events. I was able to simplify it to something that made more sense.

The install now runs as it should.