The problem with this logic is that you are still breaking backwards compatibility. Matt posted the original message because code that worked fine in 6 suddenly stopped working when ported to 7. It seems to me that it would be better to either allow it to run as it did in 6 with perhaps a note of warning in the docs, or to make it work fully. To suddenly throw an error in a place that never errored before is confusing, as is the error message itself. Our first thought was that ALTER TABLE no longer worked on cursors, since that's what the error message implied. Thankfully we have the benefit of the group mind here to help figure it out, but not everyone has that.

Thanks,

Michelle


>>>
>Why not error at the point the cursor is created?
><<
>
>Long fieldnames are valid in cursors in previous versions, this would break backward compatiblity.
>
>
>>>
>Or better yet, since it seems you can now create a cursor with long filenames, why not make everything work with the long file names?
><<
>
>This would be an enhancement request. We made the change in VFP7 to prevent data corruption, in this case the fieldname truncation.
>
>Jim