Buddy,

I have read about this before, but I thought corruption issues were prevalent 
in Client-Server and ISAM DBMS with it off. Have you done this in your 
environments before ?  and if so, what results have you seen on this ?

Frank Taylor - Director of Information Technology
F.J. O'Hara & Sons,  Inc - Araho Transfer Inc.
Boston, MA - Rockland, ME - Miami, FL
Direct Dial - 617-790-3093
email: 
[email protected]<http://mail.whitewolftechnologies.com/cgi-bin/compose.exe?id=01ef7f9322f8a76400dacb6a1fe342bb5a7&new=&xsl=compose.xsl&[email protected]>

From: [email protected] [mailto:[email protected]] On Behalf Of Buddy
Sent: Monday, December 17, 2012 9:41 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - RE: Slowness with 7.6, revisited

Karen
  You may want to look at opportunistic locking. This maybe a start for you 
http://support.microsoft.com/kb/296264

Buddy


From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]]<mailto:[mailto:[email protected]]> On Behalf Of 
Karen Tellef
Sent: Monday, December 17, 2012 8:49 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Slowness with 7.6, revisited

I had posted this question before about a client who runs 7.6 nice and quick 
with one person on, then performance slams down as soon as a second person is 
attached (takes up to half a minute to [F8] between rows of a scrolling region, 
etc).    We did an unload (clean), investigated and found a bunch of mismatched 
DLLs all over the place.  We uninstalled RBase, deleted every RBase DLL left 
out there, reinstalled and updated.  Bummer... same thing.  One person is fine, 
after that no one can move around.

I'm not a hardware or networking person, so any suggestions would just get 
passed onto their IT consultant (who the client said "I wouldn't trust to setup 
my cell phone").    It had been stressed to the IT guy to exclude all RBase 
directories from virus checking, and they say he claims he did but I have no 
idea how to check.  Even so, wouldn't the slowness happen even with ONE person 
attached if it was a virus checking problem?

Karen

Reply via email to