Login
`
Templates, Tools and Utilities
|
||
Add a comment to an Icetips ArticlePlease add your comments to this article.
Please note that you must provide both a name and a valid email address in order
for us to publish your comment. Comments are moderated and are not visible until they have been approved. Spam is never approved!
Back to article list Search Articles Add Comment Printer friendly Direct link ABC: C5B - Open and Close method problem - fix 1999-12-22 -- Mike Hanson Newsgroups: topspeed.products.c5ee
I'm not actually sure what problem your having, but I'll guess that
it's having files not opened that should be. Try this. Open
ABFILE.CLW and look for FileManager.OpenServer. Add the marked lines
so that it looks like this:
IF ForceOpen OR ~SELF.LazyOpen AND ~SELF.Info.Opened
RVal = SELF.OpenFile(HandleError)
IF RVal
RETURN RVal
END
ELSIF SELF.Info.Opened !***MH
OPEN(SELF.File,SELF.OpenMode) !Ignore Error ***MH
END
This is actually caused by a bug in the File management code. There's
an "Info" queue that is used to hold the file state for each thread.
When the last procedure in a thread closes, the queue is not cleared.
Therefore, it can sometimes be in a "bad" state when a new stream of
procedures reuses that thread number. This solves the problem. Catch
you later!
-=> Mike Hanson <=-
www.BoxsoftDevelopment.com
rlerner@ix.netcom.com (Robert J. Lerner) wrote:
>Hi Russ,
>
>Thanks for responding so quickly.
>
>>Don't use OPEN(File) and CLOSE(File). ABC will handle this for you. If you
>>must handle it yourself, then use the methods in the RelationManager.
>
>Russ, I know you can't really respond without seeing the code- but I
>
Today is November 23, 2024, 3:27 am This article has been viewed 35393 times. Google search has resulted in 33 hits on this article since January 25, 2004.
|
|