I think you might guess this could be hell to troubleshoot. My guess is the handling of integer/numeric conversion between DB2 and the VFP cursor. Can you test this with a DBC and a remote view and get the same results/error?

Using the CA, you could also try to narrow down which data type is causing the error. Eliminate all the integer fields from the SELECT field list. Test. If OK, add back the integer fields, remove date fields. Test. You may just test with fields of one data type only. Once you have nailed down what data type is causing the error, then we can move on from there.

>SelectCMD = [SELECT FUID, IDNUM, agent_id, fucode, contact, cnt_time, status, fudate, futype, resident, fuprinted, BT_1, BT_2, indvsemid, assigned, calls, last_attp, orig_fu, return2, contacted, other, notalk, callin, post_app, email_Act, fu_Act_type, create_emp, entrydate FROM BASI.CON_FUDB WHERE IDNUM = ?vIDNUM]
>
>All fields in the table are Integer, Date, or Datetime fields.
>
>
>>What is your SelectCmd? If it is parameterized, it could be that the data being returned has a field that would have a different cursor structure length based on what the data in the first record is. This usually happens if you use an RTRIM() or equivalent DB2 function in the field selection list.
>>
>>>I have a CA class that fails in VFP9 runtime when I issue a CursorRefresh or Requery.
>>>
>>>It does not have this problem in VFP8 runtime or in VFP9 IDE.
>>>
>>>The message is: View definition has been changed.
>>>
>>>I do not use a cursor schema. The table is a DB2 table on an AS/400.
>>>
>>>Any ideas why this may happen?