I have had this problem on W2k and WinNT  both.
I get the problem usally when editing the same file with rbedit when
debuging the file with trace. (edit and run, edit and run ....) 

The problem is a file lock placed on the file and that is not properly
released by the operating system while in R:Base editing the file.

The file looks good when you do a ATTRIB on the file to see the
properties. You just no longer have access to it.

The solution has been on of two things. 

1: Exiting from R:Base and then editing the file sometimes works
2: Log out of Windows and then back in almost always solves the problem.


Fred Antrobus

P.S. 
I have also had this problem on Novell file servers (v3.12) where I
actually had to power down the client workstation before the lock was
released,


On Mon, 2002-07-01 at 07:15, J. Stephen Wills wrote:
> Okay, guys, I'm hopin' f/a quick answer on this.  It might be more in the
> area of WIN2K than RBase, but, I figured, either way, one of y'all will
> probably know the solution.
> 
> So, I'm rockin' along at home yesterday, makin' changes to forms and code on
> my beautiful new laptop, moving forward with integration (-type, but a bit
> unstructured) testing, when, with all my mod's to this point working, when,
> presented in a dialogue, I get this error message :
> 
>       "-ERROR- Unable to open file: MY_FILE_NAME.CMD (2583)"
> 
> So, I check the file attributes and they appear nominal - just like the
> others.  I look at security (WIN2K) and it looks normal, too.  I check RB
> File Depth, changing it fm 5 to 10, alas, to no avail.  I'm also not aware
> of any path-related issues, and, although the path(s) are different, these
> modules are simply run fm the current directory.  Umm, yes, the file is in
> the current directory.
> 
> Additionally, I tried running it fm the R> and I got the same error mesage.
> 
> As I still have my old(-er) WIN98 laptop (BTW, anybody got any good tips on
> migration fm old unit to new one?), I'm about to copy the changed command
> files and DB to here, and try it fm here.  If it works here, then it's
> probably something related to WIN2K.  Nevertheless, I'm still lookin'
> f/help.
> 
> Thanks,
> Steve in Memphis ...
> (... where our state legislators can't seem to fund my "non-essential"
> operations, although my non-essential superiors [no insult to them] consider
> my work essential to our non-essential research group.  W/apologies f/the
> editorial whining.    -Steve)
> 
> ================================================
> TO SEE MESSAGE POSTING GUIDELINES:
> Send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: INTRO rbase-l
> ================================================
> TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
> In the message body, put just two words: UNSUBSCRIBE rbase-l
> ================================================
> TO SEARCH ARCHIVES:
> http://www.mail-archive.com/rbase-l%40sonetmail.com/
-- 
-- Fred Antrobus
-- [EMAIL PROTECTED]
-- (425)235-7796

================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
================================================
TO SEARCH ARCHIVES:
http://www.mail-archive.com/rbase-l%40sonetmail.com/

Reply via email to