I personally would not use .NET remoting if you are thinking of the future. I
would use web services or better yet WCF.

Any code you write in a web service can be transactional.

David

======================================
David McCarter [Microsoft MVP]
www.dotNetTips.com
David McCarter''''s .NET Coding Standards available at:
http://www.cafepress.com/geekmusicart.1654787045




"Tom" wrote:

> Hello,
>
> I have a Windows form application that currently uses a database local to
> the machine it is running on. We are planning on setting this application
> up for a multi-user environment, so I would like to change to a 3-tier
> architecture application for scalability:
>
> 1. My Client
> |
> 2. My Business Logic Server (The client connects here)
> |
> 3. My database server
>
> We may also create another web form client in the future, and I would also
> like that to connect to the business logic server as well.
>
> My question is, what type of communication do you guys recommend between the
> exist client and the business logic server?
>
> 1. If I use .NET remoting, can an ASP .NET page easily utilize the .NET
> remoting code if I create an additional web form in the future?
>
> 2. If I setup the logic server to provide web services to clients, I have
> heard that web services don't support transactions across multiple database
> servers, so if I can't use web services, what should I use?
>
> Any help is greatly appreciated. Thanks.
> -- Tom
>