You could design the biz object to open remote views to backend, retrieve and validate data, convert VFP cursors to ADO record sets that could be passed to the front end or even convert data to XML for inter Application data exchange. With that, the front end will not have to change nor will the middle tier if the backend changes. Only the connection in the database containing the views will change. That used to be one of the best approaches as of 2 years ago.

Have there been better theories lately to gurantee minimum code changes for different front and back ends in N tier design? Just curious.