John,

>I am coming from the VFP 9.0 world with MTS COM + objects on the Middle tier But is this the way to deploy using .net???

It's actually best to keep the business object on the workstation and the data access class on the middle tier. This is a pragmatic approach since a call to an object on another physical machine is a few thousand times slower than a call to an object on a local machine. Since all of your application logic goes in the business object, it will slow down the app quite a bit if you put the entire business object on a separate machine. However, if you only put the data access class on the server, then the business object can send only fully qualified requests to the middle tier (since the business objects will check rules on the workstation). This leverages the processing power of your workstations and keeps traffic down on the middle tier application server.

In MM .NET 2.4 you can use our web services data access class to accomplish this. Check out the MM .NET Dev Guide topic "Remote Data Access with Web Services" for details.

>I am embracing .net 3.0 / 3.5 ???

We are in the process of creating MM .NET 3.0 which will provide a WCF data access class allowing for a similar physical configuration but using the new WCF technologies.

Best Regards,