Marc,
The issue is not with the private datasession. What is happening is that you create the cursor in data session 1, the move to data session 2 and try to create another cursor with the same name.
FoxPro however does not know you are trying to create a second cursor, so what it tries to do is open the first cursor and apply a filter consistent with your second SELECT statement. Since the cursor is in use, this attempt fails resulting in an error.
Try your second SELECT with the NOFILTER keyword. I bet it will work.
Regards,
Jim Edgar
Jurix Data Corporation
jmedgar@yahoo.comNo trees were destroyed in sending this message. However, a large number of electrons were diverted from their ordinary activities and terribly inconvenienced.
