Tuesday, January 31, 2006

I remember, a while ago, two famous FoxPro gurus were fighting on what Visual FoxPro was going to be able to do running (if ever possible) on Longhorn and Avalon (now WPF).  One of them claimed that the impact of these new technologies was going to be of such magnitude that would leave VFP totally out of the game. The second guru, needles to say, denied this. It was a colorful discussion, both got carried on to a point guru #1 proposed to bet money to show how serious he was.

As guru #2, but for different reasons, I thought #1 was wrong.

These pictures speak by themselves. In case you didn't notice, it's FoxPro 2.6 DOS and VFP 9 running on Windows VISTA (formerly Longhorn) PDC 2005 build. In addition, I was able to run a FoxPro DOS program (built back in 1993) flawlessly without touching a single line of code.

But this means nothing compared to what can be seen in Ken Levy’s Channel9 video, (I recommend the whole video but, for what is worth, the fun starts at minute 21). 

Now, is it me or one of these 2 persons proved to be soooo... wrong? I am also wondering what they may think now...

posted on 1/31/2006 6:15:13 PM (Eastern Standard Time, UTC-05:00)  #    Comments [10]


A colleague on the UniversalThread  reported getting this error  when building his setup using InstallShield for Visual Foxpro

Resolving strings...
ISEXP : error -6264: A record in the Property table is using string ID 'ID_STRING1' for column 'Value' but this string is blank and the column is not nullable

I believe this problem is either a bug or corrupted ism file.

Although IS does not store data in SQL database, trying to apply similar concepts, you would agree with me that the program is trying to save a .null. value into a field who does not accept such values; since you can't modify that in IS Express for VFP, the only solution seems to be to fill that entry with some string value.

  1. Open your ism project
  2. Click on plus sign to open "Organize your setup” option branch
  3. Look for every single entry that requires a text entry and make sure there’s a string entered for each one, if not, enter some text, example being, “Publisher/Product URL” needs a string value, and so on.
  4. Rebuild your project, be happy again. If still did not work look into the rest of the project where a string entry is required and do your thing.

It is difficult, if not impossible, with this limited version of IS to determine the offending field by using the description given in the error message  'ID_STRING1'.

You could easily know this however. That is in the case you had the full version of IS Express:

  • Use the menu option "Project-Export String Table”  to create a text file with your project info. Do this at least once before you build the project the first time.
  • When you get an error, open this text file and look the value reported in the error message to which project option refers
  • Go back to your ise file and correct only the offending field.

This is how the txt file looks like:

posted on 1/31/2006 2:34:50 PM (Eastern Standard Time, UTC-05:00)  #    Comments [1]
 Monday, January 23, 2006
Technorati Profile

Trying to set it up...

posted on 1/23/2006 6:21:07 PM (Eastern Standard Time, UTC-05:00)  #    Comments [0]
 Sunday, January 22, 2006

Yeah man, yeah!.

posted on 1/22/2006 3:00:00 AM (Eastern Standard Time, UTC-05:00)  #    Comments [1]