[AccessD] Acc97: File Record Locking Count Exceeded error

Thanks Jim,

I will look into the UseTransactions property on the 
queries. That's something I hadn't thought of doing. 
Sounds like there will be a performance increase involved?

Nothing has changed on the machine that I am aware of. No 
work has been done on it recently. It's a computer that is 
used mainly for printing of bills and this once weekly 
procedure. It isn't someones desktop machine, and no one 
but myself and the two people who handle the bills and 
weekly process have access to it.

I've re-started the process on a third machine, this time 
on a vacationing managers desk, and it seems to be running 
much faster. Its still to be seen if it will crash or not.

Thanks for the help.

Ron

On Tue, 8 Jul 2003 16:24:43 -0400
  "Jim Dettman" <jimdettman at earthlink.net> wrote:
>Ron,
>
>   I'd set the UseTransactions property on your action 
>queries to no.  This
>will allow JET to breakup the action queries into 
>multiple transactions.
>Right now, it's having to create copies of everything and 
>place locks on
>everything in case it needs to roll back.  Just make sure 
>you have a good
>backup.  If the process stops in the middle, it will be a 
>mess.
>
>   Also, something has obviously changed as you said. 
> Has the machine where
>the DB's reside had any work done on it?  The machine 
>where the job is
>executed?  Remember, everything is processed locally even 
>if the DB's reside
>on a different machine, except for locking, which is 
>handled by the OS/NOS
>where the DB's reside.
>
>Jim Dettman
>President,
>Online Computer Services of WNY, Inc.
>(315) 699-3443
>jimdettman at earthlink.net