Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgrade to VFP 8.0 1

Status
Not open for further replies.

AngelaD

Programmer
Apr 10, 2002
8
GB
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?
 
Hi

There are a few, though I would not specify them as problems. Specificaly, if you have used SQL syntax, theer will be some changes and surprises.

A quick fire will be to add in your Main.PRG along with other SET codes..

SET ENGINEBEHAVIOUR 70

could solve many of the issues.

:)


ramani :)
(Subramanian.G),FoxAcc, ramani_g@yahoo.com

 
AngelaD

My company is currently upgrading to Visual Studio.NET 2002, and therefore to VFP 8.0.

A question, is VFP8.0 included in Visual Studio .NET 2002? I though it was taken out at VFP7.0? Did they put it back?

Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.
 
Rick & Mike,

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 for your help.

Angela
 
Biggest issue is sql selects with groups.

8 conforms to the ansi standard which 7 and lower did not.

See Ramani's comment above about set enginebehavior.
 
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.


Medic
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top