Bob, I'm no expert but I'm leaning toward that LAUNCH area. I'm thinking it's not clearing resources somehow.
Why don't you just use a scheduled event to run the program instead of running R:BASE and a form timer? Jan -----Original Message----- From: "Emmitt Dove" <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Mon, 21 Mar 2011 13:01:22 -0400 Subject: [RBASE-L] - RE: Network drive becomes unavailable Bob, It sounds to me as if the R:BASE session is holding resources (file handles) open on the mapped drive. Why not set up an event every 12 hours or so that causes your R:BASE app to EXIT, and in your driving batch, simply loop back and restart R:BASE? Emmitt Dove Converting Systems Architect Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Monday, March 21, 2011 11:42 To: RBASE-L Mailing List Subject: [RBASE-L] - Network drive becomes unavailable I have a v8 application that runs 24/7. It uses a form timer to run a process that sends and retrieves EDI files to FTP sites. This process runs every 30 minutes. It works like a charm... except about once a week the application crashes because the network drive has become unavailable due to system resources. I.E. If I go to MY COMPUTER and double click on the network drive (G:), I get an error message stating "drive unavailable. insufficient system resources". Only this PC is effected and it is not a network issue. If I exit out of the Rbase application, the drive immediately becomes available on the PC. (nothing else runs on this PC. It is dedicated to this 24/7 application) I have moved this application to a second PC and it demonstrates the same behavior, so it is not hardware related. The application uses several file commands performing external file functions and using wild card characters. I am wondering if this may be the issue? Such as : ERASE g:\rbti\edi_v8\ftpfiles\*.850 or DIR 'G:\RBTI\Edi_V8\ftpfiles\AWM*' (Output of the above goes into a file to obtain filenames in directory) or Zip C:\Windows\System32\cmd.exe /c MOVE &vedifile &v856file (variables vedifile and v856file contain wild cards) or SET VAR vlaunchprog = 'G:\RBTI\Edi_V8\winscp.exe' SET VAR vlaunchparams = '/timeout=15 /script=uploadAWM.txt|W' SET VAR vlaunch = (.vlaunchprog & '|' & .vlaunchparams) LAUNCH .vlaunch The applicaion also uses the "rsearchandreplace.rbl" plugin extensively on external files. Something in the code is eating up memory and not releasing it, but I have been unable to pin point the culprit. I am leaning towards one of the above. Any thoughts on memory and wild cards, zip, launch or plugins? (WhileOpt is turned off) Thanks, -Bob
