Hahahahahahaha.....



>Here is my 2 cents.
>
>Last night I was working on a project and I created a form to do maintenance of one of my tables. Because I use Codebook, i have a maintenance form subclass I used. This meant that I only had to identify the datasource, add the fields and labels to one page of a page frame, update a couple of columns on a grid and I was done. This took less than 5 minutes. I also used a combo box with a foreign key lookup into another table for one of the columns. I have a sub-classed combo box that has one property (a data environment reference) and it creates it's own data environment, with the lookup table, automatically. This took ten seconds to drop the control, size it and set the property.
>
>So the form was working, saving data, had a toolbar for navigation etc. in about 5 minutes. Do you realize what the impact of this kind of productivity is on my income? I just can't charge what i used to, to develop applications. I remember the good old days of 2.6 when these forms, even with a template, took ten times as long! This is totally unfair!
>
>So then I did have time to watch Felicity with the kids. See the kind of problems this causes?
>
>If VFP as a development tool gets any more productive, I may have to switch to VB so my productivity can be reduced to a more income elevating level. That is truly one of the most beautiful things about VB. Clients don't seem to mind that a two week VFP project can be a six month VB project. In fact, I think they appreciate it more. A big budget enhances the final products value to the corporation.
>
>Fortunately for me, I had to create a menu option, which, in the codebook model, takes longer than just about any task, especially if you try to use the builder.
>
>I think that VFP should drop this class nonsense so we can go back to writing reams of code like our VB bretheren. I mean, what would you rather have, 12 2 week projects or one 6 month project? Now you see why VB is so popular, especially for database apps.