"cursor" must be created with SELECT ... INTO TABLE (Error 1815 2

[Koen Piller]

Hi,

I have created a cursor, this cursor is used to build an other cursor in a SQL select statement.
Now I get this nasty error message, referring to the 1st cursor. The error message can be ignored and my routine will continue to do faultless the select statement.

Obviously for endusers not so good to click on an error message "ignore".

Any way to ignore programmaticaly?

Needles to say that incase I change my code into the suggestion as given in the error message the result is still the same error message.

Thanks for advice,

Jockey

 

[baltman]

You'd need to post the code for us to look for issues.

Or use your own error handler.

Brian

 

[Mike Lewis]

Jockey,

How are you creating the cursor? Are you using SELECT? If so, try adding a NOFILTER clause.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

My Visual FoxPro site: www.ml-consult.co.uk

 

[Koen Piller]

Mike,

also with the addition of the nofilter clause no difference, btw nofilter ? can't find any reference in the vfp 9.0 help although vfp recognizes this nofilter as a genuine command, will come back with on this in a new thread, after the current problem solved.

Brian,
will reduce and generalize my codinf to the bare minimum still with the error and publish a.s.a.p.

Regards,
Jockey(2)

 

[Stella740pl]

Jockey2,

NOFILTER is not a command, it's a clause in the SELECT statement, if that's what you used to create your first cursor. See this link for the VFP9 reference:

http://msdn.microsoft.com/library/d...html/c3875b75-5dc5-4eff-b33f-25b8686301ad.asp

So, if you include it when creating your first cursor, like this:

SELECT ... INTO CURSOR MyCursor NOFILTER

then you, most likely, won't get the message you are getting when you creating your second one:

SELECT ... FROM MyCursor ...

If this doesn't help, please post your code here.

Stella