>>>>>Hi,
>>>>>
>>>>>I have a routine where the application gets (via SQL select) records into one cursor from one table, then into another cursor from another table, and then again into the 3rd one. For each cursor I use value of SYS(2015). Since the SQL Select time from one cursor to another may take a second or two or could be less than a second. Can I rely that each value of SYS(2015) is unique if it is called within less than a second?
>>>>>
>>>>>UPDATE: I did a test of running from one .prg SYS(2015) one after another (obviously with less than a second between each) and all names appear to be unique.
>>>>
>>>>If you mean to use unique values for cursor names, then it's useless and you better use meaningful names. Using unique names only makes sense if you're generating a permanent table.
>>>
>>>I always thought that using meaningful names could be a problem of one cursor "stepping" on another. Thank you.
>>
>>As long as you use a different meaningful name for each cursor in the same data session, there's no problem.
>>
>>Tamar
>
>But could the following scenario happen? Say, the application creates a cursor named "MyCursor." Isn't it true that the temp folder of the PC now has a file MyCursor? Then for some reason, the application locks up and does not have a chance to close all cursors. So when user starts the application again ant it attempts to create a cursor "MyCursor" wouldn't you get a message that the file already exists?
The name of the temp file is not related to the name of the cursor, it has a random name which VFP makes sure is unique. Try
Create Cursor curDummy (Name c(10))
?Dbf('curdummy')
