Cetin,

>For UI part you might use winforms or webforms. Web service part would be done separately and needs an IIS and a proxy (or something like web matrix port implementation). If it's for intranet there isn't a need for web services IMHO.

Ok. I've been thinking that IMHO was some kind of expression like LOL. But now I know I was wrong! What does it mean?

>It'd just add another layer to fake it to be called web enabled.

Another layer of what? I'm sorry. You lost me here.

>I mean accessing say SQL server in a trusted domain just takes an IP, why would you add IIS and web service layer and its security handling.

I've done this before and it is kinda slow... or probably my design was off? That's why I was thinking that using web techno wouldn't be that bad since everyone knows that a web app is slower than a rich client app. It would be like, if someone asks why is this app slow? We could always give the wev techno as a reason...

But if you know of a way that I can create a client server app wherein users from europe can directly access our SQL server via IP and not suffer in speed, then definitely that would be the way I'd prefer to go.

I'm still kinda new to VB.NET. And I am just applying the same application design I have been using on my VB 6 apps. However, I feel that it is not the proper way to go. I still have to through the MSDN. I saw some links regarding system design .NET but I haven't really gone through it. Very busy with these killer deadlines. But I know that I have to.

I'm really facinated with the power of .NET but it's just too over whelming. Patience is the key... I know.

Martin