Ok - Here's the deal.
We have a client with around 3000 users accessing our 6.0
Fox App through a Citrix farm of about 40 machines. The backend
database is SQL Server and we are using remote views through a Fox
database. The Fox databases are hosted on the Citrix servers. Even
though the users are coming in with separate profiles, they are
accessing the same Fox database.
We found out a long time ago that FoxPro is doing a quick lock on the
database when it is opened. Because multiple users are accessing the
same database, it opens the door for a 2005 errors. As a matter of
fact, our error logs were reporting about 200 errors per day.
With SET REPROCESS TO -1 SYSTEM this should have solved the problem but
didn't. What we had to do is right a wrapper on error 2005 that calls
an API-Delay method and then a Retry, which works but is a band-aid.
It seems to me that SET REPROCESS TO -1 SYSTEM should have solved the
problem. Has anyone else seen this?
Barry Childs
Software Developer
Peak Software Systems, Inc.
Phone: (801) 572-3570 ext. 319
eMail: bchilds At peakinfo DO.T com
©2003 Barry Childs |
