>Hello
>
>How can you be confident to say that your application are SQL server compliant while you only used VFP databse with it.
>
>This application is based 100% on Views, is this enough to declare it as SQL compliant???
>

IMO, no, since you can create a view that contains internal VFP commands in various clauses, making it non-portable. You'd have to review the mechanisms used within the app to ensure that all data access refs to the system's schema are fully compliant with the SQL standard required. IOW, without ensuring that the VFP data engine can be swapped out and replaced with another to access data which is a part of the permanent database schema, you'd basically be caught in a lie if someone audited the app for compliance.

This does not preclude using the VFP engine for mid-tier and front-end layers in an n-tier implementation, but might exclude some use in data services layers.