Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP 6.0 Don't seem to be what we were waiting for
Message
General information
Forum:
Visual FoxPro
Category:
Conferences & events
Miscellaneous
Thread ID:
00100091
Message ID:
00101738
Views:
72
Josh,

My last *was* to be my last on this, BUT it seems that you STILL don't see what I am getting at, and I at least want to be CLEAR before I give up the ghost!

I am *not* asking MS or the VFP team to "solve" the problem of inherent senstitvity to corruption due to sudden power loss. What I *am* asking of them is to give US (the developers and USERS) a fighting chance to do so.

Right now it is asking a bit much to expcet *ALL* of:
1) Users who *NEVER* do anything unusual or dangerous at their terminals;
2) All user terminals *AND* network access paths to be on UPS;
in addition to the much more prevalent Server operated professionally in a secured and UPSed environment.

Giving us (the developers) the capability to design systems where ALL I/O (especially writes/updates, of course, can be done in the professionally operated and secured VFP Server would eliminate the SENSITIVITY to those two issues. That's all! Not fancy-Dan recovery. Not anything unusual. Just write/update I/O to tables done from a "safe" machine which cannot possibly fail for "silly" reasons.

I will accept that VFP could still bomb out and cause problems. I will accept that the server hardware can fail and cause problems. I DO NOT (repeat: NOT) expect VFP to do anything about these things except start up again in some 'reasonable' state, losing whatever gets lost. It would still be a damned sight BETTER than waht we get today when a DBF (or more likely its index) gets corrupted.

Cheers,

Jim N

>>I'm not asking for it to do everything. I am asking for them to address, in a certain way which I feel is quite simplistic, a very big hole in an otherwise acceptable format called the "DBF structure" - it's inherent sensitivity to corrpution due to sudden power loss.
>>
>
>Jim,
>
>This is actually an extremely difficult problem to solve. Even server databases like SQL Server sometimes get corrupted (though not as often as desktop databases). You're never going to see this feature in FoxPro or in any other desktop database. You're also not likely to see server versions of desktop databases when there are already so many good server database products out there.
Previous
Reply
Map
View

Click here to load this message in the networking platform