I found this on another support site and have kept it in case, I have been working on both in 2003 and 2008 and had a similar issue with a non-rbase file on my Server 2008. It took me a bit to figure it out. Perhaps same like post/forum or blog.....? But it helped me.
Option 1: I use a lot more of output to the local machines temp folder\filexx1x.$$$ and then share is not an issue. But not knowing the exact code and if this would cure the issue. I assumed it was a simple output file that got locked, it happens on networks. Bad or no logouts, drop packets, power etc.. the file stays open. Again assuming this is a hold by the server and not some code being processed line by line in RBase and is in a loop. I assumed this only because of no mention of declare cursor / drop cursor or if - then - while loops etc.....RBase Error Messages and the like. Option 2: Offer a way out of the locked file. Sincerely, Paul D. I stay away from SQL as much as possible. MS-SP uses SQL- I prefer using only RBase. So an easy approach for a MS-SQL issue - not my forte. I have to do it the hard way. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of MikeB Sent: Wednesday, September 16, 2009 4:45 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: Rbase won't save "RBE" changes..... Yeah I saw that too or at least a repeat of it from somewhere else: http://social.msdn.microsoft.com/Forums/en-US/tfsgeneral/thread/d1d5a9bd-9f3 7-418f-8ed6-8bb70a3d120b But it doesn't address the issue of what was causing the problem in the first place and steps to help minimize recurrances.
