Thanx John,

I'll try this and see what happens.

Luc D.


From: John Minyo II 
Sent: Tuesday, October 05, 2010 10:58 PM
To: RBASE-L Mailing List 
Subject: [RBASE-L] - re: network trouble


At 03:52 PM 10/5/2010, you wrote:

  I have developed an application in R:base 9.0 (64) under Win 7.
   
  This application runs fine and fast when run on one PC.
   
  the latest version of R:base is installed on my PC's.
   
  When I put two recent PC's in a network via a 100 Mbit/sec switch, with the 
database in a shared directory on PC A, it still runs well on PC A, but when I 
log in from PC B, it goes SLOW on this PC and eventually locks up, so that I 
have to restart R:base on PC B.
  (PC A : 6 GB RAM, 1 Tb HDD...PC B : 4GB RAM and 500 MB HDD)
   
  I don't dare to image what a disaster this could in a small network with 5-6 
workstations.
   
  It must be that I am overlooking something in the network setup.
   
  Could anyone give me 'to do'list on what to do exactly and in what order so 
to get a workable network application.
   
  This network thing is the last step I have to make in my conversion from 
Access to R:base.
  (sometimes I begin to regret I didn't stick with Access...as far as this 
network thing is concerned)....
   
  Any help would be greatly appreciated....


Hello Luc,

When establishing the database and application in a multi-user environment, 
there are considerations to make. Within the Help documentation you will find a 
chapter "Multi-User Considerations" which details settings that can be used.

To summarize, the SCRATCH setting is very important in that each users 
temporary files must be stored locally. The following is the correct syntax to 
do so.

SET SCRATCH TMP

Next, to reinforce the live database to be established in a non-editable 
structure mode and to increase overall speed, the following should be used in 
the main startup file location.

DISCONNECT
SET MULTI ON
SET STATICDB ON
SET FASTLOCK ON
SET QUALCOLS 2
CONNECT dbname

Best regards,

John Minyo II
R:BASE Technologies, Inc.
Customer Service 

Reply via email to