Peter,

My implementation of MSSQL 6.5 is part of a PERL/SQL/VFP triangle. My clients all talk to the SQL via PERL over our intranet (Mac clients). I use the VFP as a management console primarily for reporting and generation of static html pages on the system from an NT box. Our licenses are arranged accordingly.

If you go with vfp clients talking to the sql server I would expect per seat licensing to apply. Putting vfp between the clients and the sql is an interesting idea... but the licensing implications I can't guess at.

Most of my experience is PERL - SQL related so can't give much insight into the SQL - VFP angle. All of my use of the SQL is simple reading in data to VFP through remote views but not doing any writing back. For what I do, it performs well and gives me zero difficulty.

Dale