>
How and why are users going to convert to something different? >
>Well, that's not really the issue. Look, if someone is currently using DBFs and wants to stay with them, that's fine.
>
>My point was (and is), that on a new project, I would not chose VFP tables as my backend DB, even for a small app. I'd use sql express. I used it twice last year and was happy with it. I'm disappointed with the provider for VFP, and I miss out on the t-sql '05 constructs that yield additional productivity.
>
Kevin,
I agree with you 100%. If I were to start a new project today I would not use VFP tables. SQL express is the way to go. Speed of working with VFP tables is great but the time one has to spend troubleshooting data corruption is a killer. Note, however, if MS would continue supporting VFP, I would love to continue using VFP for the application development.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
