<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I am not sure what to do in this situation. But I saw this on xojo forum and maybe you can adapt their solution to your needs:</div><div><br></div><div><a href="https://forum.xojo.com/5486-how-best-to-handle-updating-one-field-in-a-bunch-o">https://forum.xojo.com/5486-how-best-to-handle-updating-one-field-in-a-bunch-o</a></div><div><br></div><div><br></div><div>I hope this helps. :)</div><div><br></div><div>Joseph</div><div><br>On Oct 8, 2013, at 11:38 AM, François Van Lerberghe <<a href="mailto:frvanlerberghe@gmail.com">frvanlerberghe@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span>As nobody answer my question, let me post it again :</span><br><span></span><br><span>I have a function (RealBasic/Xojo method) where I update every record of a</span><br><span>table (5000 records). In order to do that, I make a VCursor with</span><br><span>EVLokType.kReadWrite on the whole table.</span><br><span>At the end of this function , I call another function to update a few</span><br><span>records (50) of that same table. This update is in another function because</span><br><span>it is called by some other places of the project. How must I deal with the</span><br><span>records locking in this second Vcusor using the same table, but not the same</span><br><span>records ?</span><br><span></span><br><span>1) If I nil the first Vcursor (locking the whole table) before create the</span><br><span>second, locking the needed records, I have a risk (very low I know, but that</span><br><span>exist) that, just before I create my second Vcursor, another user lock some</span><br><span>records of that table, reading or writing incorrect data and stopping me to</span><br><span>complete the work.</span><br><span></span><br><span>2) Must I keep the first Vcursor ensuring that nobody can modify the table</span><br><span>and create the second with kNoLock ? Is it safe to update the records in</span><br><span>this second Vcursor ?</span><br><span></span><br><span>3) I see a third option : Keeping the first cursor. I pass this Vcursor as</span><br><span>parameter to iterate, test each record and update the records that meet some</span><br><span>condition. I don't like this option as</span><br><span>- I prefer sending a second SQL query to retrieve the needed records rather</span><br><span>than iterate and test each record</span><br><span>- this second function is called by some other places of the project</span><br><span></span><br><span>I prefer the second option if it is safe. Could you be kind enough to give</span><br><span>me your advice on this ?</span><br><span></span><br><span>François Van Lerberghe</span><br><span>Rue Thier Monty, 15 A</span><br><span>4570 Marchin</span><br><span>Belgium</span><br><span></span><br><span>_______________________________________________</span><br><span>Valentina mailing list</span><br><span><a href="mailto:Valentina@lists.macserve.net">Valentina@lists.macserve.net</a></span><br><span><a href="http://lists.macserve.net/mailman/listinfo/valentina">http://lists.macserve.net/mailman/listinfo/valentina</a></span><br></div></blockquote></body></html>