Peter,

Barring a tit-for-tat comparison of VB and VFP, I'd just say generally that the more enhancements you put into your application, the less thin your application becomes. It's an obvious tradeoff, and yes, to add things like tooltips, you could build client-side ActiveX components to distribute. Also, I think IE5 might have some built-in tooltip stuff with DHTML. BUT, specifying IE5 makes your application less thin and you start heading for a thick application. It's a tradeoff that the IT manager has to decide upon.

My opinion is to go with Microsoft's near-term/long-term goals, which is IE browser, COM layer, and SQL Server database. Specifying IE to my customers is not exactly a thin approach, but it does give them some very nice advantages (client-side application deployment is minimal, lower hard disk and memory requirements, server-side processing for less network traffic.)

If Microsoft changes the rules, I'll adjust accordingly. I'd rather not fight upstream. Just going with the flow over here...

Scott


>>He said we should move our VFP code to COM objects in the middle tier, use HTML/ASP for the front-end, and SQL Server for the database. It was a direct question I asked at our PAFox.org user group meeting. I asked him, "What should we do as VFP developers?" Ask him yourself. His email address is acoupe@microsoft.com.
>
>
>Scott, I'm interested in light-weight front-ends. I would like to know more about what I (the users) would give up. I have heard "no tool tips" for instance. What else?
>
>I like to block entrance to fields when they are not needed with When methods. Can I do that type of thing with HTML/ASP? AFAIK VB does not have a When equivalent. You can disable a field from somewhere else but the logic is quite different.
>
>All tidbits are of interest.
>
>Peter Robinson