>>All I can tell you is that VB is not allowed at my agency any longer for large systems, only PB and vfp. VB is not considered a good tool for large sytems.<
>
>Bruce,
>
>You mean our gov't figured out something before many large US corporations did????? Oh wait, let me guess. Some statistician at your agency compiled some statistics on project length when VB was used and when VFP was used.
>
>Creating a graph with length of project development as (y) vs. complexity of app as (x), he found that VFP had a line with a rise to it. Not too big a rise since using OOP can leave you with not a lot of work to do after you have designed most of your base classes for the app. However, the line indicating VB required a second piece of paper to draw the line for a complex project. The line just shot off the graph.
>
>I'm going to have to show your comments to some slow IS manager types I know who are still trying to grasp the "should I use VB cause MS says to" question.

Actually, the primary large-app tool that the 'Systems' people use here is PB (so don't tell them that part :). A good number of us outside Systems use vfp, however, and I'm trying to get vfp on the Systems standards list now, in a stealth way by getting VS approved. And at least PB is a respectable tool for serious apps, compared to VB...VB classes are only given now for end-users, in the same minor league as Access.