I found it. Form A creates a cursor in the default datasession and does a SET FILTER to LocalVar. Form A is relased, and Form B takes over. Problem is that the LocalVar is now gone, thus causing me to have a filter set to something which no longer exists - thus the error. geeeeezzee man!

>There are no realations really for the cursor. The only thing odd about the cursor is the fact that it's another screen that creates it, and the error is appearing in another form. I used the 'default' data session, and the 'object' that's created by the form is not destroyed when I issue the GO TOP command. (VFP will waste the created cursor when the form-object disappears). I'm baffeled because the error doesn't make sense - it seems like VFP thinks I've got char's where numbers go or something........
>When I run the debugger, I open the data-session window. When I click on the cursor it gives me some weird object/form reference error - but then the cursor pops up non-the less. (with correct data). It almost seems like VFP doesn't know where to look for the cursor - pops up the error - then finds it.
>I'm kinda lost on this one, and I gotta have it figured out quickly becuase this bad-boy goes into production this weekend. I'm about to put a cheezy ON ERROR do nothing piece of code around it or something. aaaaahhhhhhhhhhh!!!!!
>
>>>I have a form that uses a temporary cursor. All works well, except at one point I have:
>>>
>>>SELECT DiamondCursor
>>>GO TOP
>>
>>How about relations? How about if you pare everything out so you do nothing but create the cursor and execute those two lines?