WRITE+CLOSE vs CLOSE (was Re: Screen ghost?? SOLVED BUG???)

[Kenneth Brody]

On 1/6/2010 1:31 PM, ivan wrote:
> Since my system call worked from an @key I decided to move my call statement up to the front of my processing then move it down the chain until it failed.  It didn't fail until the lookup I do to the file that I do right before my system call, but write and close it before I do the system call .  And then I started to play around with that string of code until I came to the problem.
>
> Before I did the system call I do a lookup to file.  I fill in some information then I 'write' the lookup, then I 'close' the lookup.  Then I do a system call that opens a screen and allows all of the processing on that file to check info that is entered in that file.  This has worked fine for years, but recently that changed.  It seems that if I leave the 'write lookup' command in there, followed by a 'close lookup' command, then the system call just locks, If I comment out the 'write lookup' and just leave 'close command' in there everything is fine!
>
> Is this a bug or is this something that is to be expected?
[...]

There is no net difference between WRITE+CLOSE versus CLOSE, since the CLOSE 
will implicitly write and unlock the record before closing the file.

-- 
Kenneth Brody