I would think winforms are better also. But I've been asking around at events I've recently attended as well as reading up. People I've talked to at events are rarely, if ever, working on winforms projects. And it appears that 80% of job openings require asp.net.
>Anything that's intensively data entry, I believe, will be better with WinForms. You can still utilize "web technology" by using Web Services to interact with your backend data store.
>
>Take this advice "with a grain of salt" however, as I develop almost exclusively with .NET WinForms and I *definitely* prefer WinForms over Web Forms. <g>
>
>~~Bonnie
>
>
>
>
>>Hey Guys!
>>
>>From VFP standpoint, is it advisable to go directly to Web Forms? Or Win Forms would still be viable long term? Our system involves heavy inputs of data because it's a manufacturing system including Payroll, Accounting, Production, Inventory, etc.
>>
>>I tried toying into Web Forms but the way I see it, it's not RAD yet. There are a lot of annoying beheviours even in design. Laying out screen design is not that easy. Another thing is the postback events...
>>
>>TIA
(On an infant's shirt): Already smarter than Bush