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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Taking the next step (licensing and upgrading) 2

Status
Not open for further replies.

tatonka

IS-IT--Management
Aug 20, 2002
27
GB
I want to increase the number of FPW2.6 users on my network but this means that I will exceed the number of user licenses available. I have spoken to Microsoft who have advised me that Visual FoxPro licenses are down gradable and that open licensing would be my best option.

This appears to be an opportune moment to think about upgrading some applications to VFP but I am concerned that the very latest version will be too much for FPW2.6 to handle. I am looking for some advice regarding both the licensing (is there another way) and upgrade (where do I start, which version is most suitable) issues.

May be I should I ask this question on the VFP forum?.

I am using XP workstations on a NT server.
 
Are you talking about developer licenses? If your application(s) use the FPW runtime files these are "unlimited". The downgrade option basically says that you can buy any current version (6/7/8) of VFP and instead of installing it, you can run any (one) of the earlier versions of FoxPro. Note: This new copy has to be a "full" version - not an "upgrade". If you choose to install the new version, then you must stop using the "old" one. When you downgrade, you are responsible for acquiring the files necessary to install it on a new system - of course since you already have copies of FPW this shouldn't be a problem.

Note: I am not a lawyer, so it's always best to contact MS and make sure my understanding is what their and your lawyers deem it valid.

Rick
 
Thanks Rick,

I don't pretend to be a programmer (well, sometimes jokingly I do) and have inherited a number of workstations that have the full version of FPW2.6 installed. The numerous bespoke systems that we have running are located on a server and are called by each workstation using a c:\foxpro\foxprow.exe –t [server drive letter]:\foxpro\[calling program or screen] command or similar.

Reading between the lines I am guessing that FPW runtime files are used to create self contained applications that don’t need the full application installed on a workstation to run and don’t require individual end user licenses? If so, can you point me in the right direction to find out more about runtime files and how to create self contained applications?

Do I need a developer license to create them and/or any additional software?
All I currently have are full versions and licenses as mentioned.

Thanks in advance.
 
Rick,
Do you have a view on what would be the most sensible version of VFP to try and upgrade FPW2.6 to?
Can I jump directly to V8.0?
 
Well, using "c:\foxpro\foxprow.exe ..." implies that you are running the full developer edition from / on each workstation. Unless you've got one of the very rare unlimited licences of FPW, then you either need to be licensed for each of these workstations (expensive), or consider building an .APP / .EXE and using the royalty free Runtime Files.

With FPW 2.6, there were two levels of Developer licences - one with the ability to create .APP / .EXE files and a cheaper one that couldn't. (See for some details on the versions sold and current "availability" and pricing.)

While you can jump to VFP 8.0 and most of your code will "run" as-is, VFP is a whole new world and any applications should normally be rewritten rather than simply converted.

Also, be aware that the table structure for VFP .DBF's is slightly different to accomodate the new features in the last 8+ years, and once a table has been updated the old FP can't use them. (On the other hand VFP can use the "old" DBF's without any problem. My company has been running a FPW 2.6a, VFP 5.0 and VFP 6.0 app that shares the same data - even running at the same itme on the same system - for 3+ years at multiple multi-user sites!)

Rick
 
Thanks for your reply.

After a quick investigation I discovered that the Build Executable is greyed out in the Project Build dialog box so I guess that I have the cheaper version? (however, Build Application is selectable). FPW Help refers me to a Distribution Kit? I think I’d better make some time to investigate further.

On the VFP front, how much of a new world is it? Could a pseudo programmer make a home there and be happy? Seriously, is it possible for you to summarise the key differences or point me in the direction of a man who can?
 
The lack of a Build .EXE option is indeed the first clue you have the standard version versus the "Professional" version. Luckly if you get the Distribution Kit, you can effectively upgrade.

While I could start by telling you all the differences between FPW and VFP, the biggest is 8+ years in OS changes and what user's and developers expect in a Windows database development environment. There is a whole different mindset in designing Windows Event Driven apps that the "modal" DOS like world that FPD/FPW used. (Remember while FoxPro for Windows looked like a Windows program, it was really just a graphic make over of FoxPro DOS.)

Could a pseudo programmer make a home there and be happy?
Well that's one of those "maybe" answers. A lot will depend on your background, your understanding of current Windows concepts, your motivation and the time you want to spend.

I'd suggest that you first go to and explore - there is a great deal of information here. There are even links to the full MSDN VFP online Help for VFP 7.0 at (this will be updated to VFP 8.0 in the near future).

You can also go to where all the "best" VFP books are. Most can be purchased as eBooks, and many have free chapters you can download to evaluate.

Finally, you might want to go to the VFP forum here on Tek-Tips and post a similar question. There are a lot more people with VFP experience there that I'm sure will provide you with an opinion. Note: I've been programming professionally for 37 years, and the last 14 years almost exclusively in FoxPro, and I learn new stuff most every week. I "haunt" the forums and newsgroups to learn things as much as to answer questions.

Rick
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top