>Hi,
> My company just get a project that required to build a client server application with VB as Front End and VFP as Backend. My client has 5 braches, 2 of them located in different location and others are in the same building but different floor.
> Do you have any hints to do this? Any comments or conditions should be considered?
> Where should I place my DLL (business rule), client workstation or server? Should I develop it as Intranet or normal Win32 application?
> Any sample code and article about this?
>
>Please advise for any comments/recommendation.
>
>Thank you very much

Have you considered an Intranet solution for this problem? If so, take a look at west wind web connection.

I am not really any kind of expert at this < g >, but you can place your COM biziness objects on the file server, where they can access the VFP data very quickly. The biz object can return the data to the VB clients as ADO. The VB clients can manipulate that data, send the ADO record set back to the biz objects, and they in turn update the VFP data. Simple, huh < g >?

The advantages to this are:

1. You are acessing VFP data with a VFP COM object.... very quick
2. You are passing data over the wire as an ADO record set, rather than the VFP way, which may clog your pipes.

There are a lot of good VFP frameworks out there. I am using Mere Mortals, and it would be a very good fit to your problem.