Backgroundworker and OleDbConnection

Question

0.00/5 (No votes)

See more:

I am new to VB.Net. I have a backgroundworker routine that shares OleDBConnection with UI. Note when backgroundworker uses OleDBConnection, it's not used by UI routines. The strange thing is when I run the program in design environment (visual basic express 2010), it works fine. But when I run the executable in other computers, it stops at OleDb.OleDbDataReader line. I use connection.open and .close statement throughout the program - again it works in the design environment. Has anyone seen this? What do I need to do?

Posted 28-Apr-13 3:51am

Member 8475769

Add a Solution

1 solution

Add a Solution

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2013-04-28T08:55:00

Solution 1

Don't "share" a single connection object through out your code.

Create a new object when you need it, use it, dispose it when you done with the query. There is no advantage to "sharing" a single connection object throughout your code.

Posted 28-Apr-13 8:55am

Dave Kreskowiak

Comments

Member 8475769 28-Apr-13 17:58pm

Thank you for your quick reply. I tried to dispose reader as well as the connection every time I used the query, but still the same happens - it works when I run it through Visual Basic 2010, but it doesn't work when I run it as an executable in other computers. This happens only for the backgroundworker routine. UI routines that use queries are fine.

Dave Kreskowiak 28-Apr-13 21:01pm

Well, without seeing the code that's failing, it's pretty much impossible to say whats wrong.

Backgroundworker and OleDbConnection

1 solution

Solution 1

Add your solution here

Preview 0

Backgroundworker and OleDbConnection

1 solution

Solution 1

Add your solution here

Preview 0

Existing Members

...or Join us