Visual Foxpro 9 Free Download Full Version
Sanora Ngueyn
I'm not using Git as full version control, i.e., the version will be controlled by myself such as MyProject01, MyProject02, etc. Git will be using (git init) for each individual directory. I just want to use Git as multi-developer environment for my Visual FoxPro desktop application development.
From january 2014 there is a new replacement for scctext(x).prg called FoxBin2Prg, which can convert VFP 9 binaries to text (prg style ones) and can regenerate the binaries from this texts. Can be used to Diff and Merge code and the generated text can be modified, and the changes reflected on the regenerated binaries.
If you don't want histories, then diff and patch will serve you just as well. In git, in addition to having multiple branches in a single repository, you can also create multiple working copies by cloning the repository. Having multiple branches allow you to preserve histories from previous versions while also allowing you to go back to a previous version and make modifications; having multiple working copies allows you to run multiple versions of the program simultaneously or store files that were not checked in but is version specific (e.g. sqlite database file). There is no reason to reset revision history every time you create a new version.
Yes, you can do that because in a DVCS you can push or pull from any repository to any repository (this is what differentiates distributed VCS from centralized VCS, the other main difference is that in DVCS a working copy is always also a repository with full history instead of just a snapshot of a specific revision). With that said, setting up a bare repository is still a good idea to make code sharing easier. If PC02 need to push but PC01 isn't online, then PC02 would have to wait until PC01 is online to be able to push, a bare repository on a server that is always online wouldn't have that problem.
We have been working with VFPSCM.exe tool since 5 years in large projects with 300 forms and 20 classes, and we have never loose any code, and the must important we have the SCM ready, visualizing only the changes made, and a history of commits, that convert in our logbook of changes.
Basically, Microsoft wanted a stronger presence in the database market and they were in severe need of database products, people, and technology. Fox Software was a perfect fit for them. To give you a little more context, in 1992 the xBase market was still booming, Access (Cirrus) was still in development, Visual Basic 1.0 had been released and VB 2.0 was in development, and the first release of SQL Server for Windows was not until 1993.
Power Users: Going all the way back to dBASE you could question whether it was a platform for power users with development capabilities or a platform for developers that power users could use. It was both. Visual FoxPro put it squarely in the developer category, and Access took over as the preferred database for power users. The result: much fewer licenses sold.
VB, SQL Server, .NET: VFP faced a lot of competition from other products within Microsoft. With the emphasis always on the latest trends, many developers felt compelled to move to other technologies.
People had been foretelling the death of FoxPro since Microsoft bought it in 1992. What made 2007 the year when Microsoft finally decided to cancel it? Had sales declined to the point that Microsoft could no longer justify Fox development? Did they want to use the Fox Team in other parts of Microsoft? Did big customers move to something else? Were the people that cared gone or no longer in a position to do anything about it? Your guess is as good as mine. We will never know.
In the initial years after the Fox Software merger, Microsoft put a huge effort and lots of resources into creating VFP 3.0. There were about 50 people on the Fox team with a big marketing budget. In the following years, both Access and VB grew in market share and also competed in ways with the VFP market (and messaging), and by the time VFP 5.0 was released, many upper managers wanted Microsoft to just end VFP there. In fact, they did for a short time. I was there, in a meeting with 40 people, and the formal announcement was made to the Fox team that VFP was dead. It was very early 1996, and that meeting lead to the Gartner Group releasing their report that VFP was dead, which had a major impact on future VFP sales.
I have been a vfp developer since 1997, and the cancellation of vfp by microsoft pains me. To me developers be it of vfp or any other platform are always left orphaned wen such cancellation happen, bearing in mind that they have big applications developed on this plaforms that are running out there and it will take more than time and money to convert the to new platforms.
dBASE was first exposed to me almost 30 years ago (in early 1980s). I have been developing PC applications for over 20 years using dBASE, FoxPro and VFP5. I regret that Microsoft has not developed anything for me (or any other VFP developer) to convert or at least help convert a VFP application into another language. As Microsoft Office continues to evolve, my VFP5-based applications are no longer compatible with Office 2007 and beyond. I can no longer invoke an Excel worksheet and send data to it. Can anyone tell me whether this problem can be solved if I upgrade my VFP5 to VFP9?
Hi everyone, I am using VFP9 and I frankly tried to switch to the new Era, by trying MySQL and even SQL Server, but very frankly i find VFP much more powerful in terms of an effective relational database that you can link to as a developer from any other RAD or GUI development tool to create your user interface to make modern looking and appealing.
In the regard of discontinuing FoxPro, I suggest for a class of world wide developers to take the responsibility to handle the development of VFP on their own, like what Delphi developers did in Lazarus (Free Delphi RAD).
Thanks Ashraf Sada. Have you made any progress of using VFP 9.0?
If you have, please guide me. I can even pay you a price for it, if it helps using VFP 9.0 after Sedna.
Your quick answer will be appreciated!
Hi Guys,
I am a Foxpro developer, as I have been since 1991. I have had my grounding in dBase 111 Plus, Foxpro For Dos from 2.0 to 2.6, Visual Foxpro 6,7,8 and now 9. Visual Foxpro 6.0 and 9.0 are the best of the group by far.
I continue to develop and use the product with other engines like MySql.
I intend to push foxpro to the limit and create data storage linkages with other engines using foxpro as the application development environment and report generation engine. Foxpro 9.0 has the capacity to allow for the creation of classes to provide functionality for cross-platform access and manipulation.
Just wanted to thank you for the great write up. I have finally been able to sleep at night since I stopped supporting all those named vendors. I retired in 2009 and have not missed a single day of the confusion and frustration brought about by the product support supplied by the various vendors of dbms. I am sure there is a special place in Hell reserved just and justly for them. Thanks for the trip down memory lane.
While a decision to replace this app is still underway, I continue to keep this old girl ticking away (it has it temperamental moments, with new versions of Windows. But, we manage to keep things moving).
I love to see others still running some DOS applications. I am not a developer per say. I learned enough to keep a SBT system going my employer purchased. And when the hardware cash registers we purchased for way more money than they should have been died I wrote our cash register program and we are still using it today.
I am being forced now to upgrade to Windows 7 32 bit and my Dos Foxpro software works just fine in it. I had a little problem with some of the Windows Software I wrote in Visual FoxPro5 when I did the change to Windows 7 but with the help of good people on forums I got it all ironed out.
I even found a piece of software from Italy that works great to capture the LPT out put to a windows printer and it works Great. Its called Printfil and they have a website at Printfil.com. I am not involved with them in any way other than being a customer!
You might first visit one of the FoxPro forums such as Universal Thread, Foxite, and others to see if they can recommend a solution to your problem with VFP 6. VFP 9 is definitely the best version of FoxPro, while retaining backwards compatibility, so it should run your existing code with few if any changes. VFP 9 SP2 included changes for better compatibility with Vista, which means it also runs better on Windows 7 & 8. My VFP apps run fine on Windows 8.
Hi All,
32-bit is coming to an end and so it seems is my VFP. I have several clients across the country that have been using my software for more than 20 years. Virus protection is also vanishing into oblivion and the hype is for 64bit and cloud. I have to find an alternative and rewrite Accounting and Points of Sale systems.
Win8.1(x64) does not allow me to install VFP9 and I one has to work with two networked desktops next to each other to assist in the translation process. The keyboards and mouses (mice) are forever in the wrong place. It is a nightmare!
I am extremely comfortable in all the above technologies but I can EASILY EASILY EASILY say that Visual FoxPro was the absolute best development environment ever. It blew away VB 6.0 and access is a sad joke of a database. I worked projects with VB/Access 15 years ago and it actually enraged me that it was more popular than VFP.
I lost faith in VFP when it did not embrace the internet. I learned ASP and then ASP.NET and I would have loved to have seen what VFP could have done with web development had the team been given their druthers.
I am glad I made the transition away from VFP when I did as I got to finally get into heavy web development which I felt sheltered from in my VFP days. The web was sexy and well desktop database development; not so much. Well at least VFP was a contender. I think everyone who was lucky enough to have a long run in VFP must have done something right in a past life because VFP just had so much good karma.
7fc3f7cf58