>>Clicking the link on the page will answer some questions that have surfaced around here. One that comes to mind right off the top of my head is:
>
>Here's my fave:
>
>How do you position Visual FoxPro in relation to Microsoft Access?
>
>Microsoft Access, the database in Office, is the most broadly used and easiest-to-learn database tool that Microsoft offers. If you are new to databases, if you are building applications that take advantage of Office, or if you want an interactive product with plenty of convenience, then choose Access. Visual FoxPro is a powerful rapid application development (RAD) tool for creating relational database applications. If you are a database developer who builds applications for a living and you want ultimate speed and power, then choose Visual FoxPro.
>
>Bad ass... thats what we wanna see...

In other words, if you're more likely to order a Happy Meal with the infant toy, choose Access. If you like a steak dinner with all the fixings, choose Visual FoxPro. <g> Hmmm... I think I feel a Jeff FoxWorthy thread coming on: "You might just be an Access developer if..." Nah, I'll resist. <g>