Phil, You never mentioned what version you were running. Some time back there was an ongoing thread discussing problems with using an UPDATE within a CURSOR loop. There were apparent problems with the automatic locking mechanism I know that the developemnt team has worked hard to eliminate these problems. If you are not using RBASE v6.5++ in-line patch one, then you should update and see if this corrects your problem. If you are using the lastest update then you would do us all a great favor by reporting you problem as a bug to the RDCC.
-- Jim Bentley American Celiac Society [EMAIL PROTECTED] - email (973) 776-3900 x5029 - voicemail/fax ---- "Phil Nolette" <[EMAIL PROTECTED]> wrote: > What is interesting is that in the processing of these > 120,000 rows of data, > if I use an update command to record the conversion status > (CONV = Y/N) then > I run into a virtual memory problem about 75% into the > conversion (12-15 > hrs). What I have been doing is to create a conversion > status table and use > an insert command with the key of the target conversion > record with the > status. It runs more effeciently than the update and I > do not have a > problem with the virtual memory. What this leads me to > believe is that an > update used in the manipulation of a cursor does not clear > all of the memory > used and eventually "gags" itself. > Phil __________________________________________________ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com ================================================ 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
