At 12:25 AM 7/9/2013, James Bentley wrote:
Bruce,
I would move the DROP CURSOR c1 command to just after setting the
error messages off. The reason to do this is that the CURSOR might
use some of the tables you are attempting to drop. If a table is
part of a CURSOR a DROP TABLE command will fail in the CURSOR is
still defined.
Programmatically, you could also take advantage of the newly
introduced (CHKCUR('cursorname')) function, if you wish.
(CHKCUR('cursorname')) checks to see if a cursor is declared and is
not dropped. The function returns an integer value of 1 if the name
exists and is not dropped, and 0 if it is not declared or dropped.
-- Example
IF (CHKCUR('c1')) <> 0 THEN
DROP CURSOR c1
ENDIF
This is as simple as it can get.
A declared cursor must be dropped prior to dropping the table/view.
Internal Lock Error, Resources Unavailable Error, and I/O Errors
are the result of such mismanagement.
Very Best R:egards,
Razzak.
www.rbase.com
www.facebook.com/rbase
--
30+ years of continuous innovation!
15 Years of R:BASE Technologies, Inc. making R:BASE what it is today!
--
--- RBASE-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [email protected]
(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body,
place any
text to search for.
================================================
