Mark,
Maxframe isn't n-tier, but it DOES work well with SQL-Server (and presumably other client-server backends). I am presently rewriting a VFP5 app into a VFP6 + SQL-Server and almost every form is translating just fine.

The biggest problem was the client stating 2 years ago (in writing, we insisted) that "Since we will never need to go to SQL-Server we prefer you to use the speed of SEEK and native VFP files". So every data call has to be rewritten..... NOT, however, a MaxFrame problem.

We kept the Maxframe-specific files in the DBC, upsized everything else to SQL-Server with the Upsize wizard and haven't had any problems. If the client insists on having the Maxframe files in SQL-Server as well, we'll add a "SQLEXEC()" to load them into VFP cursors. We tested it and it works fine.

HTH
Barbara

>Thanks Doug
>
>Following your advice I have read up on Maxframe and it is the front runner
>for me at the moment because it seems the most flexible and won't get in my way.
>
>I am a bit worried that it is not n tier and as a result may be due for a major overhaul (Its been around a long time)
>
>Many Thanks