>>Pretty much all I can find is maintenance work too. I'm between a rock and a hard place. I dont know which way to go. Do I start learning Java, or should throw myself into the .NOTYET architecture?
>>>
>>>Flame away. I have nothing to be ashamed of. I've been using VFP for a long time now and used it to build all sorts of applications. I love VFP but I also love to develop new software products, particularly on the web. I'm seeing a lot more opportunities to do this using VB/SQL and ASP (and .NET in the future) than I am with VFP even with slick tools like WebConnect out there. With VFP, most of my projects have been maintenance-oriented. Since I've been using VB/SQL and ASP, I've been involved with developing new products which in and of itself is very rewarding, despite the shortfalls of VB (admittedly there are a few).
>>>
>>>Regards,
>>>
>>>-JT
>
>.NOTYET - LOL! I haven't heard that one dot yet!
>
>Yes, 'tis a quandary which road to take. I've thought about learning Java myself, simply because there's the most amount of web dev for individuals with Java skills (includes JSP, EJB, JDBC, JINI, etc.). For myself, I think it makes the most sense to get up to speed on .NET and XML first because I've already got a comfort level with the current MS status quo (SQL/VB/ASP).
>
>Also, my current employer is using all MS so it makes the most sense for me to stay with the MS platform but I would like to do full-time consulting some day so that may change my strategy. If I find that .NET is limiting my contracts (including legacy VB/ASP), I'll look into joining the dark murky primordial underbelly of Java Enterprise development. Hopefully, this won't be necessary!

Aye! XML is the way to go, but Java will go anywhere. Unfortunately, I can't, so I'm kind of spinning my wheels a bit. Maybe I should drop it into third gear, let go of the wheel and see where I end up.