>>Educate me. Perhaps everyone would have a better understanding if you could >give us a real world example where VB and Access are preferable to VFP.
>
>Reason 1: There are no real DB-intensive operations going on. So, Access will work fine. Also, we are not talking millions of records here, only thousands.
>
>Reason 2: There needs to be some level of security in the DB. Access has it - VFP does not.
>
>Reason 3: VB is a much lighter-weight UI than VFP.
>
>Reason 4: And this may be the most important one: The client wants VB as the front-end, Excel as the decision support tool, and Access as the data store.
>
>Since I can work with these other tools, and it technically makes sense to use these other tools - and that is what the client wants - that is what I will use.
>
>
>Simply put, it isn't a VFP only world out there

Thanks, John. I guess most of my experience is rooted so deep in xbase it's hard for me to see any other type of solution. I'm trying to see the light... I've begun to see the light. And that being said, as president of the user group here in Phoenix I need to maintain some degree of loyalty. They don't call me the Fox-Nazi because I don't have any opinion on the subject (:-)