Assuming this is a marketing issue - I'd use the term "smart client" <g>

yag

>Assuming the following general architecture...
>
>- .NET app using WinForms at the client end with Rich UI
>- A few validations in the UI, but the vast majority of business logic is in C# in the middle-tier, called from the UI through a Web Service 'function channel
>- SQL Server back-end
>- Crystal.NET runtime running locally...
>
>Would you call this a 'thin-client' app. Some in our company are tempted to, but I have stated that since we're using CR.NET locally to generate reports, we can't call it thin-client.
>
>Thoughts?
>Kevin