Don't be surprised. Around here I'm faced with several "programmers" who feel that Access is the only database that should be used, other than SQL Server of course. However, they get pretty quiet when I show them a web application developed in VFP and Web Connection that only takes a fraction of the time that they were planning to spend using ASP pages, Access, and SQL Server. It amazes me how many people seem to think that SQL Server is needed in all situations when they find out that Access just doesn't cut it in the enterprise.

How does this all happen? Mose people don't ever think for themselves but merely follow whatever a multi-billion dollar corporation tells them is the proper way of doing things. (Use this same analogy to figure out why the United States will soon have the coronation of GW Bush, a complete idiot underserving of the presidency who will obtain it merely because his father was president.) Someday someone will publish an expose on how many businesses that insisted on hiring VB programmers to do database applications were duped into wasting huge sums of money when an elegant and much cheaper solution that was in the same box of software was never used because it wasn't actively marketed by the company selling the software.


By the way, for everyone predicting the ultimate death of VFP now that VB will be object oriented: It seems to me that you have a two year window before this technology will even be released/usable considering that the first version will be unacceptable to upper management and will most likely be full of bugs. My current philosophy is to use the best tools for the job, learn a little VB on the side (come on now, it really isn't hard), and then if and when VB has all of the same features as VFP, switch to VB. Of course, there may eventually be a VB backlash once all of upper management realizes that they've been fooled for so long and had an object oriented language right under their noses all the time.

Regards,

Mark Beno