Eric ---

Could it be that your paths to the tables in the database are screwed up? Are you moving the DBC before compiling? Try doing a VALIDATE DATABASE in VFP5 after moving the DBC or whatever you are doing before the VFP6 compile. If the VALIDATE comes back OK, then go to VFP6 and COMPILE. Also, are you sure that you don't have any PATHs in a VFP5 CONFIG.FPW that are not carrying over to VFP6, therefore not allowing VFP6 to find tables associated with the DBC?


>>Hi Eric,
>>
>>>Anybody know why fields with more than 10 characters in the name get trimmed when ported to VFP6?
>>
>>Sounds like you are creating free tables which only support field names with 10 characters. Where yo you port from?
>>
>>Christof
>
>It is a VFP5 .dbc that is simply recompiled in VFP6. In some cases the field name is trimmed but the index expression remains the same. So I get a variable not found error and any bound controls or access through code is hosed. The tables were never free as far as I know, they were always linked to a database. Interestingly enough, I can simply edit the name of the field in the table designer and it keeps the old name. But it is a pain in the rear. ;)
>
>Eric K.