From: anotheranne@nomail.co.za   
      
   Hi, all.   
      
   There is always a hassle to contend with when setting up my paradox   
   automated student used book purchase system each year (this network put   
   up yearly at this time for a Feb and Mar run). It involves bringing in   
   windows computers (we run linux for everything else now) and setting up   
   the network and getting it all running. This year we had a really   
   frustrating time, and I hope you won't mind if I share the problem and   
   solution with you.   
      
   Following a 31st Jan 2003 post from Liz on configuration issues we have   
   been glued to the letter of the law ever since. At first we did think   
   this was a configuration issue and spent a lot of unnecessary time   
   chasing this line, particularly of course the path to the .net file,   
   local share, etc.   
      
   The problems were twofold   
   1.  the operation of the main .fsl was very slow, you could almost see the   
   form think   
   2.  we could only run the server and one client m/c or lockups occured   
   and then we found pdoxusrs files in \\servername\C\Pdoxdata\myapp\Private   
   whereas they are set to reside two steps back from that in the PdoxData   
   directory.   
      
   In the end we had to conclude the issue did not resolve around settings   
   in idapi or indeed any software issues. I note that all machines run   
   their own version of pdox9 with the same bde config file copied to all   
   clients. A model pdox setup that I felt in the end was not at fault.   
      
   I work from home & ssh to the office, use a GUI client to access our main   
   postgresql database across the net, or ftp files to and fro. And here a   
   few weeks back was an issue. All of a sudden we could not ftp, all other   
   connections yes, ftp no. No amount of investigation would solve this but   
   I had become suspicious of the router as the ftp setting on the NAT page   
   had evaporated and subsequently reinstatement did not give ftp access.   
      
   This in fact was the key to the whole issue. When we decided to swap out   
   the router with a replacement we were back to normal. Full speed, all   
   clients connecting and running fine.   
      
   So I wouldn't pretend to know the inner workings of pdoxusrs.net and .lck   
   files, but obviously a poor LAN connection can have a serious affect on   
   client-server operation. A salutory lesson in keeping the hardware up to   
   scratch.   
      
   hope that all of you regulars are keeping well.   
      
   Just for the record, this is a dlink router. I am looking for a   
   replacement with the admin page accessible via a text-only browser like   
   w3m since this is what I have on the server box. A long shot, but any   
   suggestion welcome.   
      
      
   best regards   
   Anne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)