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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
VFP 7.0
- Thread starter nguyen12
- Start date
jackstrawn
Programmer
If you mean Tool Tips in a form:
* Form Property
ShowTips=.F.
Don't fully understand the report page number chop. Normally when something is "chopped" in a report it is a result of the label size too small to display the value/text.
Jack Strawn
* Form Property
ShowTips=.F.
Don't fully understand the report page number chop. Normally when something is "chopped" in a report it is a result of the label size too small to display the value/text.
Jack Strawn
- Thread starter
- #4
Thanks for your help. I also have another question. I am trying to design a report. I decided to put my column title and fields in a horizontal accross. When i do a preview of my report, i got an error message saying detail field is too large to fit on page. Any suggestion. Thanks
GaryWilsonCPA
Technical User
A little off topic but since you are all using 7.0 did your projects built in 6.0 migrate over with ease?
I have something built in 6.0 and want to install 7.0 and not rebuild project.
I have something built in 6.0 and want to install 7.0 and not rebuild project.
Gary,
First, you are right, this really should be a new thread, since someone else needing this info might not look here - however ....
You will have no problems using VFP 6.0 and 7.0 on the same system (unless you choose to chasnge the default location and install it in the same directory!). I've been developing both types of projects on the same system for about a year and a half now, with no conflicts.
If you "migrate" a VFP 6.0 project to VFP 7.0, there are only a couple potential problems. One VFP 7.0 tightened up the syntax checking in places so you might get errors where none existed before. (e.g. Declarations didn't require commas between multiple entries before but now do. So LOCAL a b c - was fine before but 7.0 requires LOCAL a, b, c .) Also, since there are a number of new built-in commands, they may conflict with your own functions (especially if you require different parameters).
The internal structure of the menu file is different so one you open a 6.0 menu in 7.0, it will be converted and won't work back in 6.0.
Last (?) if you choose to implement any of the new database events, then the dBC will be changed so VFP 6.0 won't be able to use it.
In reality it's pretty transparent, and in fact in the VFP 7.0 development environment you can run (almost) any VFP 6.0 .APP or .EXE without even recompiling!
Rick
First, you are right, this really should be a new thread, since someone else needing this info might not look here - however ....
You will have no problems using VFP 6.0 and 7.0 on the same system (unless you choose to chasnge the default location and install it in the same directory!). I've been developing both types of projects on the same system for about a year and a half now, with no conflicts.
If you "migrate" a VFP 6.0 project to VFP 7.0, there are only a couple potential problems. One VFP 7.0 tightened up the syntax checking in places so you might get errors where none existed before. (e.g. Declarations didn't require commas between multiple entries before but now do. So LOCAL a b c - was fine before but 7.0 requires LOCAL a, b, c .) Also, since there are a number of new built-in commands, they may conflict with your own functions (especially if you require different parameters).
The internal structure of the menu file is different so one you open a 6.0 menu in 7.0, it will be converted and won't work back in 6.0.
Last (?) if you choose to implement any of the new database events, then the dBC will be changed so VFP 6.0 won't be able to use it.
In reality it's pretty transparent, and in fact in the VFP 7.0 development environment you can run (almost) any VFP 6.0 .APP or .EXE without even recompiling!
Rick
- Status