My company is currently upgrading to Visual Studio.NET 2002, and therefore to VFP 8.0. Is anyone aware of problems upgrading from v6.0 to v8.0 that I should be aware of?
I have now found out off our technical support that, as you say, VFP 8.0 is not included in Visual Studio.NET 2002 - it was included in the build because it is the global corporate standard. It would appear that certain parties are trying to foist an upgrade on us by giving the impression that we have no choice. I now discover that if we have strong objections to VFP 8.0, then we are not required to upgrade (which I wasn't told at the start of the project - don't you love office politics!). However, from what I have gleaned off the web, it looks as if there shouldn't be too many problems - so we shall try out a few applications and see how it goes.
Thanks guys, for that illuminating tips on VFP8's SQL command.
I was about to post a question on this issue when I saw this thread.
I've been using VFP8 for almost a month now. I thought this SQL problem was a bug. I never knew this was a sort of syntax change.
I'll try Ramani's solution.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.