Re: Recommendation for database access
- From: "code3_brent" <code3brent@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 23 May 2005 18:35:02 -0700
I've been through all of this initially. It is not consistent, so if I made a
change, it may be a month before it crops up again. But when it happens, it
is a critical app. So I need to find an alternative.
"Stephen Howe" wrote:
> > 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.
>
> Ask them questions:
>
> 1) Are they all experiencing this problem or does it happen to be a
> particular user(s) or a particular PC(s)?
> 2) If it is a few PC(s) find out if anything has changed recently on the
> PC's, other than the new antivirus program
> 3) Ask them if they could try using your product with the antivirus
> disabled. Does it suddenly rework?
> 4) If the antivirus product is enabled, is it enabled to scan all disk
> access? If so, can the database be excluded from the scanning (usually you
> can).
>
> Stephen Howe
>
>
>
.
- Follow-Ups:
- Re: Recommendation for database access
- From: William \(Bill\) Vaughn
- Re: Recommendation for database access
- References:
- Recommendation for database access
- From: code3_brent
- Re: Recommendation for database access
- From: Stephen Howe
- Recommendation for database access
- Prev by Date: Re: Recommendation for database access
- Next by Date: ADO connectstring for SQLServer not port 1433
- Previous by thread: Re: Recommendation for database access
- Next by thread: Re: Recommendation for database access
- Index(es):
Relevant Pages
|
|