Well of course there are!! Would we be doing this if it didn't work?

Our application is a Records Management System for the fire service (fire departments). It's more than just client/server, it's SOA (Service Oriented Architecture for those that are wondering), meaning we use Web Services exclusively to communicate with the server-side stuff.

I'm not sure how many customers we have (I'm not in marketing <g>), but we have large installations (meaning big fire departments with many stations) and they are all happy with the performance of the application.

I don't know why Jordan has had such a bad experience with .NET, but we've had no major problems.

~~Bonnie


>Thanks for everybody who replied to me on the topic of "Application Architecture".
>After my conversation with Jordan. I'm wondering if there is any successful Client/Server .NET application with MS SQL as backend and the .NET application as the client application. If anybody could share their success stories or failure stories, I would be most grateful!