Skip to main content

Working Between Visual FoxPro 8 and 9

Many developers have production applications running with one version of a runtime yet do development in a later version. This lets daily work take advantage of the newer productivity tools while the final application is still using the older runtime. The challenge here is ensuring you don't use features in the newer version in code that will run in an older version.
 
A great example is using MESSAGEBOX() to show numbers or dates. Recent versions of Visual FoxPro let you do a MESSAGEBOX(5) and it will do the internal translation between the numeric value and the string equivalent. Seemingly a very simple function yet if you get used to using it, and then have to run on an older version of FoxPro that doesn't support it  - you get a invalid type error message.
 
Likewise with VFP 9 and VFP 8 but this time, it's something a little more hidden. VFP 9 allows developers to take advantage of MemberData, the ability to extend the property sheet further with your own goodies. VFP 8 doesn't have this feature. Yet when working with the two versions side by side, it always seems as though you can write in one and then produce in the other. This is almost true.
 
If you specify member data in a class in VFP 9 (and this can be done very easily using the add-ins provided on the Solutions Sample page), you won't be able to edit them in VFP 8. Instead, you'll get errors where VFP can't find the correct memory variables. The solution is to manually open the VCX or SCX file, find the Properties field with the memberdata in it and remove it.
 
At the bottom of the memo field, you'll see a line that says Name = "classname" but everything before it will be square boxes or binary data, just remove everything from the line that says _memberdata = and all the way down. Then you'll be able to open your class again in VFP 8 and earlier versions.
 
Yes, you will lose your Memberdata (like Favorites, and advanced editors, etc) but the value of cross-version compatibility is far greater, in my opinion.
 

Comments

Post a Comment

Popular posts from this blog

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...
Post a Comment
Read more

Respect

Respect is something humans give to each other through personal connection. It’s the bond that forms when we recognize something—or someone—as significant, relatable, or worthy of care. This connection doesn’t have to be limited to people. There was an  article  recently that described the differing attitudes towards AI tools such as ChatGPT and Google Gemini (formerly Bard). Some people treat them like a standard search while others form a sort of personal relationship — being courteous, saying “please” and “thank you”. Occasionally, people share extra details unrelated to their question, like, ‘I’m going to a wedding. What flower goes well with a tuxedo?’ Does an AI “care” how you respond to it? Of course not — it reflects the patterns it’s trained on. Yet our interaction shapes how these tools evolve, and that influence is something we should take seriously. Most of us have all expressed frustration when an AI “hallucinates”. Real or not, the larger issue is that we have hi...
Post a Comment
Read more

Friend vs Therapist vs LLM: Shades of Grey

The conversations with AI series brings up a single point and then compares it between different LLM engines. These types of conversations were one of the many contributing factors to my writing of " Towards Consciousness " that explores the benefits and issues of creating a conscious AI. In this scenario, I was interested in seeing how an LLM might differ from a friend or therapist on issues that may have nuanced responses or contexts. In doing so, I came up with an interesting discussion on shades of grey. My Premise: Is it a bit strange to be using an LLM as a sober second thought? Every time I walk down this path of “why use an LLM to do certain things”, I come back to the alternatives that people like to say. “Why not bring it up with a friend?” A friend typically has your back or will say whatever to support their own agenda. “A therapist?” That’s someone who is “trained” to be impartial. But a computer? A computer is impartial based on two logical outcomes. If you say ...
Post a Comment
Read more