none
Where to get a license Visual FoxPro 9.0 RRS feed

  • Question

  • I still have FoxPro programs still running to this date. Some of my clients want to have their licensed Visual Foxpro 9.0 as government agencies are intensifying their crackdown against software piracy. 

    Thanks.

    Friday, June 21, 2019 8:17 AM

Answers

  • You just thanked me above for answering this question. No version of VFP is legally available for sale now except through MSDN.

    Tamar

    Friday, June 21, 2019 8:32 PM
    Moderator
  • Again said: Your customers don't need VFP to run your application once you compile it into an EXE (or EXE+DLLs) and provide the roaylte free runtime, maybe even a setup. Ther DevOps/Admins can install an MSI package you can create with install shield on single desktops and with MS administrative tools like SCCM, that's not even your business.

    But there is NO need to have licenses for running a VFP application, once it is build to an EXE, there are no license fees or CALs for data access too. Nothing like that.

    Just get the building process straight and don't distribute source code files or even a VFP project, ie learn how to really build an application. To start with just click the BUILD button on the project manager. Also learn about what the main file of a project is and that the easiest way is to have a main PRG file and also learn about READ EVENTS and what is and isn't available in EXE vs IDE, eg the IDE toolbars is not, yet _SCREEN remains available and it's easy to create a menu that has many/almost all the menu options (via "Quick menu").

    There is no need for customers, neither private nor government to have VFP itself just to run a VFP application, it just needs to be correctly built and distributed with an installer and runtimes. What you can't distribute is VFP itself and so tools like table designer, but who needs that? Your audience ae end users, not developers.

    VFP comes with Installshield Express and even with merge modules you need in such a Windows standard installer to provide the runtimes (bot C++ and VFP). Others pick the free inno setup system and you find a lot of info about using Inno to distriubute your final EXE.

    It's a hurdle, once you have an EXE it simply runs on your PC but not on others, because it's not all in one file, it never is, also not in other programming languages. So don't get the wrong ide the EXE build process is buggy. a C# EXE only runs on other computers without a setup, as the .NET Fraemweork is already a Windows component. If you distribute an EXE made with the newest Visual Studio targetign the newest Framework you will also need to provide a setup installing a newer .NET Framework in the installation process.

    Distribution and Setup is part of the develoepr knowledge, don't skip that, it's like being a baker only knowing how to make dough, but not how to bake it.

    So again what you were already told and ignored:

    -You have VFP as a developer, you finally build an EXE
    -You create a setup, which packages your EXE, ActiveX controls you used, VFP runtime DLL and Data files (DBFs etc) and provide that to customers.
    -They don't need anything but that!
    -What you are allowed to distribute is listed in HOME()+"redist.txt" (that means in the file redist.txt of your VFP installation home folder). 

    redist.txt also points out the article in the help telling more about distributable files (and restricted):
    https://docs.microsoft.com/en-us/previous-versions/visualstudio/foxpro/chk1kkwc%28v%3dvs.80%29

    And that is part of the topic "Distributing Applications":
    https://docs.microsoft.com/en-us/previous-versions/visualstudio/foxpro/we0w55zb(v=vs.80)
    There really is everything you need to know in the VFP developer help.

    Tricky parts of the setup is providing shared data to a multi user application. The best way is to either do this as manual one time setup on site yourself and have a default configuration to a file share or make that a separate server setup. If the backend is SQL Server it bescomes a job for companies or governmental organisations to strreamline this into their server licensing, so you could be fine providing a bak Backup file or mdf/ldf to attach to a server. And (again) a configuration option to use a connection string or DSN for the link of your frontend application and the backend data.

    Aside of that, you also find a walkthrough about the process of creatíng a setup in the VFP help, it is all there:
    https://docs.microsoft.com/en-us/previous-versions/visualstudio/foxpro/akzettd8%28v%3dvs.80%29
    Or going the Inno Setup route:
    http://doughennig.com/papers/Pub/InnoSetup.pdf

    Bye, Olaf.

    Saturday, June 22, 2019 9:11 AM

All replies

  • You just thanked me above for answering this question. No version of VFP is legally available for sale now except through MSDN.

    Tamar

    Friday, June 21, 2019 8:32 PM
    Moderator
  • Again said: Your customers don't need VFP to run your application once you compile it into an EXE (or EXE+DLLs) and provide the roaylte free runtime, maybe even a setup. Ther DevOps/Admins can install an MSI package you can create with install shield on single desktops and with MS administrative tools like SCCM, that's not even your business.

    But there is NO need to have licenses for running a VFP application, once it is build to an EXE, there are no license fees or CALs for data access too. Nothing like that.

    Just get the building process straight and don't distribute source code files or even a VFP project, ie learn how to really build an application. To start with just click the BUILD button on the project manager. Also learn about what the main file of a project is and that the easiest way is to have a main PRG file and also learn about READ EVENTS and what is and isn't available in EXE vs IDE, eg the IDE toolbars is not, yet _SCREEN remains available and it's easy to create a menu that has many/almost all the menu options (via "Quick menu").

    There is no need for customers, neither private nor government to have VFP itself just to run a VFP application, it just needs to be correctly built and distributed with an installer and runtimes. What you can't distribute is VFP itself and so tools like table designer, but who needs that? Your audience ae end users, not developers.

    VFP comes with Installshield Express and even with merge modules you need in such a Windows standard installer to provide the runtimes (bot C++ and VFP). Others pick the free inno setup system and you find a lot of info about using Inno to distriubute your final EXE.

    It's a hurdle, once you have an EXE it simply runs on your PC but not on others, because it's not all in one file, it never is, also not in other programming languages. So don't get the wrong ide the EXE build process is buggy. a C# EXE only runs on other computers without a setup, as the .NET Fraemweork is already a Windows component. If you distribute an EXE made with the newest Visual Studio targetign the newest Framework you will also need to provide a setup installing a newer .NET Framework in the installation process.

    Distribution and Setup is part of the develoepr knowledge, don't skip that, it's like being a baker only knowing how to make dough, but not how to bake it.

    So again what you were already told and ignored:

    -You have VFP as a developer, you finally build an EXE
    -You create a setup, which packages your EXE, ActiveX controls you used, VFP runtime DLL and Data files (DBFs etc) and provide that to customers.
    -They don't need anything but that!
    -What you are allowed to distribute is listed in HOME()+"redist.txt" (that means in the file redist.txt of your VFP installation home folder). 

    redist.txt also points out the article in the help telling more about distributable files (and restricted):
    https://docs.microsoft.com/en-us/previous-versions/visualstudio/foxpro/chk1kkwc%28v%3dvs.80%29

    And that is part of the topic "Distributing Applications":
    https://docs.microsoft.com/en-us/previous-versions/visualstudio/foxpro/we0w55zb(v=vs.80)
    There really is everything you need to know in the VFP developer help.

    Tricky parts of the setup is providing shared data to a multi user application. The best way is to either do this as manual one time setup on site yourself and have a default configuration to a file share or make that a separate server setup. If the backend is SQL Server it bescomes a job for companies or governmental organisations to strreamline this into their server licensing, so you could be fine providing a bak Backup file or mdf/ldf to attach to a server. And (again) a configuration option to use a connection string or DSN for the link of your frontend application and the backend data.

    Aside of that, you also find a walkthrough about the process of creatíng a setup in the VFP help, it is all there:
    https://docs.microsoft.com/en-us/previous-versions/visualstudio/foxpro/akzettd8%28v%3dvs.80%29
    Or going the Inno Setup route:
    http://doughennig.com/papers/Pub/InnoSetup.pdf

    Bye, Olaf.

    Saturday, June 22, 2019 9:11 AM