Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Window7, 32 bit, XP mode no longer works
Message
De
27/08/2013 10:05:57
 
 
À
27/08/2013 09:30:30
Metin Emre
Ozcom Bilgisayar Ltd.
Istanbul, Turquie
Information générale
Forum:
Visual FoxPro
Catégorie:
FoxPro 2.x
Versions des environnements
Visual FoxPro:
FoxPro Dos
OS:
Windows 7
Network:
Windows 2008 Server
Database:
Visual FoxPro
Application:
Desktop
Divers
Thread ID:
01581381
Message ID:
01581504
Vues:
72
>>I don't own that code base. I gave my labor to it, but it's owned by another entity. I am happy
>>to advise the processes we went through though to help re-create a community version.
>>If interested, let me know.
>
>You say, there is an auto-converter written and advice write again it. Can't you persuade them
>make this code for public-domain?

It is not possible due to their positions on software.


> I know you're a share believer... :)

I am. I have desired to move my entire career into the areas of what I call "liberty software," which is copyleft protected open source software. It is the focus of every effort I have in my life outside of the rigors of maintaining a family, etc.

--------
As for this product, it will also generate the equivalent T-SQL commands directly from VFP source code. It was created as a way to upsize from older FoxPro versions to newer ones, and the big component is from DBC containers and stored procedures to use SQL Server.

It is a true auto-converter, but it does need some "coaxing" and maintenance from time to time, because as we encounter new variances in code it sometimes fails. Some of these fixes are mere changes to tables and data. But others are actual logic bugs requiring reprogramming.

For example, a couple weeks ago one of the developers added some code to a FPW 2.6 screen. He manually added a simple @ SAY command in a custom code block. But, his addition was the first time in any of the nearly 1,000 screens and over 10,000 @ SAY and @ GET commands, where an @ SAY was given without having a FONT attribute coded afterward. So, my code did not know to check for NULL pointers for the "FONT" keyword or anything which came after in the @ SAY lines because it had never been seen in the code base before.

The tool we'd been using for about a year (called "FCON" for FoxPro Converter) was essentially broken, preventing the build from completing, until we discovered the cause. It took about an hour of tracking down. :-)

So ... little issues crop up from time to time. For what it knows about, it is fully automatic.
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform