Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Andrzejek on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Macola v7.5- Files easily corrupted
- Thread starter bUAYa99
- Start date
You are working with technology that is at least 12 years old, on a platform that neither Macola nor Pervasive supports. So this is going to be hard to answer. Is anyone experiencing Macola errors - other than the obvious error 002?
What are you doing to fix the corrupted files?
Software Sales, Training, Implementation and Support for Macola, Synergy, and Crystal Reports. Check out our Macola tools:
What are you doing to fix the corrupted files?
Software Sales, Training, Implementation and Support for Macola, Synergy, and Crystal Reports. Check out our Macola tools:
I cannot tell you why your macola.btr file is getting corrupted.
Be we have been running 7.5 under btrieve for -- you guessed it -- about 12 years. It is very uncommon for any of our files to become corrupted. Pervasive (btrieve) is very stable for our us.
Be we have been running 7.5 under btrieve for -- you guessed it -- about 12 years. It is very uncommon for any of our files to become corrupted. Pervasive (btrieve) is very stable for our us.
If your files are getting corrupted often, then you are either
1. Hosting your files on a Novell Server. Even though Novell owned Btrieve for some time, large files on Novell get corrupted often.
2. Having problems with your network. Btrieve/Pervasive has no error correction as it works at a lower layer of the network stack before error correction applies. What this means is that if you are having dropped packets, then you will have corruption of btr files.
3. Btrieve is not configured properly.
Any of this sound like your situation? Please note, that dropped packets usually go undetected in most networks as most software works without errors after the lost packets are resent. If you do have problems with other software, it would probably manifest itself with the "General Network Failure" error messages.
Scott Travis
1. Hosting your files on a Novell Server. Even though Novell owned Btrieve for some time, large files on Novell get corrupted often.
2. Having problems with your network. Btrieve/Pervasive has no error correction as it works at a lower layer of the network stack before error correction applies. What this means is that if you are having dropped packets, then you will have corruption of btr files.
3. Btrieve is not configured properly.
Any of this sound like your situation? Please note, that dropped packets usually go undetected in most networks as most software works without errors after the lost packets are resent. If you do have problems with other software, it would probably manifest itself with the "General Network Failure" error messages.
Scott Travis
- Status
Similar threads
