IMHO I am in agreement. While we are working in such a great development environment (e.g. today I completed many reports Access was not designed to handle) we are hamstrung in so many ways by the mere presence of SUBS(programsourcetitle,1,3)="Fox". A few times, I have develped some solutions for clients and not told them until AFTER acceptance the source language. More than a few bemused grins, I can assure you. Given the tools, capability and wide range of application potential - perhaps "DB Solution" as a title. Just my 2cents.
R
>I've been using Foxpro since it was Foxbase+ and believe it can do 99% of what I ask or want it to do. It just has a name "Foxpro", that has come to symbolize (to some at least)a product that is not robust or professional enough for project development. I believe its time for MS to rename Visual Foxpro and give it a name that more accurately reflects what it is today.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only