Skip to main content

I was bit by a 2.6 year old Fox(Pro)

Talk about old ghosts coming back to haunt you.

I was upgrading a customer's old Foxfire! installation from version 3.0 to 8.0. They were running Foxfire! 3.0 under FoxPro 2.6/Windows.

But they had this one report that kept on crashing under the 8.0 version that would run fine under their old version.

I tried to run Foxfire! 3.0 under a copy of Visual FoxPro and it crashed there as well.

Hmmm...what could it be? I looked at the SQL generated.

There was the problem that was causing the crash: one of the relationships was referring to a field that didn't even exist.

The field in the SQL referred to a field named PART_SEC_ID_I but the real field was called PART_SEC_I.

But why didn't it crash under the older version?

The reason? FoxPro 2.6 ignored the extra fields.

I opened up the table in FoxPro 2.6.

? part_sec_i
** returned a value
? part_sec_id_i
** returned the same value.

Sheesh...I can't believe we were actually able to build quality applications back then but then again, when our tool wouldn't even tell us we were wrong in our field names - who needed field validation?

Now the fun part - how to tell someone that even though their old application worked great, it was actually not reporting a problem it should have been.

Comments

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

Who Wants To Be Logical? I Do! I Don't! (with Claude)

In my book, Towards Consciousness, I explore PET , a theory that attempts to explain consciousness and possibly how it might apply to AI. As part of the conversations with AI series, I've included this conversation with Claude.AI in which we were talking about something very different and yet the conversation redirected itself back to PET. For the record, there is no such thing as "Colfsity". A It's interesting to me that people want to proclaim their distinction from being rigid and unlike machines, yet they also complain that the "best" people keep a rigid schedule, regular routines and logic understanding of issues. That's a perceptive observation about a real tension in how people think about themselves and what they value. There does seem to be this paradox where rigidity is simultaneously rejected as "robotic" or inhuman, yet praised when it appears as discipline, consistency, or logical thinking. I think part of what's happening is t...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...