I am in a different vertical market but deal with a similar custom base (in terms of number of people using the application). I am leaning towards window forms with thick clients. I know that existing customer will be happy. The only reason I am going back to thinking Web forms is marketing/sales. People just love to hear "web-based" these days (whether they really need it or not).

Thank you for sharing.

>We are also looking at that. Realistically, it will boil down to the costs involved up front and for longterm maintenance (as well as man-hours). It is a business app that is really customer driven. Most of our customers are small businesses (ideal for VFP) with anywhere from 3-20 workstations. The average is about 5. They prefer thick clients and having their data stored locally. We utilize webservices now in our VFP9 app for transferring licensing information and for other functions such has updating financing guidelines, etc. We also download policy data direct from insurance carriers and 3rd party servers daily. We only have a small customer base who would prefer a thin client and perhaps data hosting on our server so we are looking at webforms as an option but it probably is not likely given our customer base.
>
>
>>Tracy,
>>
>>In your initial message you mentioned (if I remember correctly) that most of your study is to decide on approach of UI -> MT -> Database. I was wondering (I apologize if you already talked about it and I missed it) if you are planning your future application UI to be in Win Forms (windows) or Web Forms (ASP)? I am kind of sort of going through the same process in my head for my application, and for me a major decision is what to user for UI: WinForms or WebForms. I am changing my mind (conceptually) back and forth every day <g>.