>>>>Hi All!
>>>>
>>>>Im running my app with some Select INTO CURSOR.
>>>>
>>>>Sometimes I get the above error from VFP my code samle is as this:
>>>>
>>>>SELECT p3.dato,p3.ansatt,p3.ordre,p3.skift,;
>>>> p3.avdeling,p3.jobb,p3.fastlonn,p3.fastdel,;
>>>> p3.pverdi,p3.timer,;
>>>> IIF(p3.snittlønn>maxlønn,maxlønn,p3.snittlønn) AS snittlønn;
>>>> FROM proshoyv14 p3;
>>>> INTO CURSOR andreprodukt1
>>>>
>>>>IF USED('andreprodukt')
>>>>sele andreprodukt
>>>>USE
>>>>ENDIF
>>>>
>>>>USE dbf('andreprodukt1') AGAIN IN 22 ALIAS andreprodukt // here I get an error but not in all
>>>>situations??
>>>>
>>>>Best regards
>>>>
>>>>Per Simmersholm
>>>
>>>The file for a cursor may or may not be a file on the disk. You need to:
>>>
>>>USE (dbf("andreproduckt"))...
>>>
>>>Vlad
>>
>>I thought that once you close a cursor, it is gone for good (at least, it can be). Isn't that it's nature? It is a TEMPORARY file.
>>
>>Joe
>
>So? I don't get the point here.
>
>Vlad

andreprodukt1 & andreprodukt...didn't see the '1' at the end of the first cursor name...I thought he was closing the cursor right after he created it...minor complaint: I wish that when examples are shown, people would keep them as simple as possible. Why a long select statement followed by a cryptic filename (or in this case, cursor)? When not , , etc...to make it obvious that we are talking different names. I personally don't have time to go through the logic of a long select statement and be picky about filenames, variable names, etc...I want to look quickly, see if I can help, and move-on...now, you might want to say "Well, if you don't have time to give a question the proper attention, don't get involved", but my point is still valid: Keep it simple and clear. More people will take the time to give it a look and it increases your chances of getting a good answer and it decrease your chances of confusion.

Sorry for the confusion.

Joe
Joe

Joseph C. Kempel
Systems Analyst/Programmer
JNC