>Here is the scenario:
>
>Existing VFP code, moving to SQL Server, DBA wants to change field names to match company standards, we are using CursorAdapters to access SQL Server and create VFP cursors.
>
>I know I can define the CAs to map new field names to old field names so much of the existing code can continue to use the old field names. However, DBA is offering to create SQL Server views to present the data with old field names.
>
>I've never used SQL Server views, so I'm wondering if there is much of a performance hit when they are used vs just going directly against the tables and mapping the fields in the CA definition. Seems to me that SQL Server view would add some overhead, but what do I know? :-)
>
>Awaiting your wisdom...

I have **NO** wisdom to offer on this, but find myself asking 'wouldn't the DBA offering the views not offer them if they were bad?'.

cheers