Hi Ross,

The key to a successful C/S front-end is in how well it performs. VFP's advantage is it's local database engine - which is largely irrelavent in C/S scenerios - especially since ADO is here. ADO is based on the Fox cursor engine. VB is much better equipped to handle this stuff as VB supports data bound ActiveX Controls.

Where VFP fits in is the middle tier. In a C/S environment - VFP is just too fat. It takes a min. of 4 megs to get things running in VFP. For VB - you need about a meg.

Don't get me wrong - I am a VFP fan. However, even with OOP - VFP does not have an advantage as a C/S front-end as opposed to VB. If you want reusable components in VB - you can make use of VBCCE - which is pretty cool when you think about it. Then, your controls can be hosted by just about anything - Office, IE, even VFP.