>>>>>When I run a standard report on a Cursor, I get that message. The cursor is updateable, since I create it using the USE DBF AGAIN ALIAS method after an SQL creation.
>>>>>
>>>>>When I suspend the calling program, the cursor is selected and appears just fine. I know that wizard reports have problems with this, but this isn't one.
>>>>>
>>>>>Any ideas?
>>>>
>>>>Yes, look at your report very carefully. One mis-labeld field can cause this error. You could have 99 valid aliases & one tucked away where it is hard to find that is bad.
>>>>
>>>>HTH,
>>>>Tom
>>>
>>>You got me started on the right track, anyway. I've scrapped the old report and created a new one. With one field on it, there is no error (hooray!).
>>>I recall now having problems once or twice in the past where a field was hidden behind band separators, etc., that caused such problems. It's probably something like that.
>>>
>>>Thanks,
>>>Bruce
>>
>>
>>Yep, like I said, 99 good ones & 1 bad hidden way in the back... (g)
>>
>>Tom
>
>I actually got a late-blooming brainstorm (nice metaphor?) and looked in the bad FRX as a table. There was an old variable listed in there that had no V/H position, and was causing the problem. A hypothesis is that it had something to do with the fact that I converted the report from 2.6.

Bruce

Yeoow! Not good....

Tom