Re: Error when connected to Access MDB
sterling_at_fiac.net
Date: 05/04/04
- Next message: Richard: "Re: Timestamp Value - please help"
- Previous message: William \(Bill\) Vaughn: "Re: Bulk Inserts"
- In reply to: VB Programmer: "Error when connected to Access MDB"
- Next in thread: VB Programmer: "Re: Error when connected to Access MDB"
- Reply: VB Programmer: "Re: Error when connected to Access MDB"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 4 May 2004 03:16:49 GMT
If you use Microsofts ODBC.NET Data Provider instead of OleDB.NET, it will
let you have more than one connection to the database, it creates a
connection pool. When using OleDb to open a database it locks the database,
and it has a time out of so many seconds before it releases the connection
something like 10 secs after its closed. When your using the ExecuteReader
no matter what the provider is, you can't use the same OleDbConnection to
execute another instance of ExecuteReader with the same OleDbConnection. If
you open Component Services and find the connection that has been created
for your application you will see that when your application runs it will
create a service for the application when it executes. You can manually
release the connection, so you don't have to wait for OleDB to release it
while your testing your code.
Hope this helps.
Sterling
- Next message: Richard: "Re: Timestamp Value - please help"
- Previous message: William \(Bill\) Vaughn: "Re: Bulk Inserts"
- In reply to: VB Programmer: "Error when connected to Access MDB"
- Next in thread: VB Programmer: "Re: Error when connected to Access MDB"
- Reply: VB Programmer: "Re: Error when connected to Access MDB"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|