Jim,

I'm in a strange place with my growth as a developer. I've been using OO stuff for years (Visual FoxPro), but probably only partly as I should. I'm the only developer in my company and (with regards to VB.Net), I don't really have anyone I can turn to and say "hey, I'm stummped here... would you look at this and see if anything jumps out at you." or "That's neat. How'd you do that?" or .... well you got the idea.

So, while I know the words you said, and that they are right, I have gaps in my ability and knowledge that prevent me from knowing if I've done as you suggest.

Would you be willing for me to email you my project, so you could look it over and give me your advise? My app is small, only 1 form, 1 database with 12 tables (most of which are small lookups). I'm not asking you to do development, or to take me on as a student (but if you offered that I'd be interested in talking more about that). I'm just looking for a good shove in the right direction, and maybe a small flashlight and rough map to find my way.

BTW - your name sounds familiar... did you ever work in Tampa, or write a book?

Rick
----------------------
>Richard,
>
>If you have properly written your business logic into classes independent of the GUI, then all you should have to do is re-write the interface to the business classes. The great thing about this approach is that you can have implement both a fat client (windows forms) and thin client (webforms) frontend to your business logic.
>
>If this is not how your application is architected, I would highly reccomend writing it that way when you re-tool for web forms.
>
>regards,
>
>JE
>
>>I have an app I'm building. It's currently a Windows form. I now need to end up with a WEB form.
>>
>>Is it easier and wiser to start from scratch as a WEB form, or is there a conversion tool?
>>If there is a conversion tool, then is it something worth using?
>>
>>Thanks.
>>Rick