Recommendation for database access
- From: "code3_brent" <code3brent@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 23 May 2005 15:15:15 -0700
I have a VB6 application written a few years ago that pulls data from an
Access database via ADO. There are about 15 users throughout a large network.
All data access is read only. Every single recordset is specified to open
read only.
This application was running fine for over a year. All of the sudden, the
client started to get errors that said that the database was in use by
another user and couldn't be opened. I banged my head against the wall for
weeks trying to figure out what was going on, but couldn't find it. It was
not consistent and not re-creatable. The only thing that came up was about
the time this happened, they implemented a new antivirus program.
I created a temporary fix for it, but I am now going back to addess this
again. I thought of using ADO.NET, but am afraid I will eventually run into
the same issue. I have also thought of exporting all of the data to an XML
file, which shouldn't have any locking problems.
Just wanted to get some input as to how others thought I should proceed. I
need to charge them a fixed amount for the changes, so if I run into problems
again, I end up eating it.
Thanks for your input!
.
- Follow-Ups:
- Re: Recommendation for database access
- From: Stephen Howe
- Re: Recommendation for database access
- From: Val Mazur \(MVP\)
- Re: Recommendation for database access
- Prev by Date: vb.net - datagrids inserting records
- Next by Date: RE: Access 2000 to 2003.
- Previous by thread: vb.net - datagrids inserting records
- Next by thread: Re: Recommendation for database access
- Index(es):
Relevant Pages
|
|