Skip to main content

Data Integrity with VFP 8 and Older Code

I was working on a problem earlier this week with VFP 8 (SP1) and an application that has been "upgraded" over the years from DOS to Windows to VFP. With any such application, unless it's been lucky enough to receive a complete re-write, there are always lots of older pieces of code that are running around that do FLOCK( ), RLOCK()  and the like.
 
When this application was first distributed, an alarming number of "record is in use" messages occurred. And it was determined by the company's development and support staff that it was because of change in VFP 8 with the new SET VALIDATE TO, which creates better corruption awareness. As a result, we immediately switched all their customers' SET VALIDATE to a value of 0, to minimize the problem.
 
But now the problem seems to be resurfacing. Obviously, this is a case for "why aren't they using TABLEUPDATE() ,buffering and etc?" but I'm wondering - has anyone else seen this problem with older applications recompiled under VFP 8 or is it simply the case of an older application needing a wakeup call?
 
(yes, things like network issues, etc are being looked at but it's very interesting that it only occurred in a more recent version). If we find an obvious reason in the meantime, I'll be posting it but it's an interesting scenario.

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

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

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP