Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 725
  • Last Modified:

Corrupted MDX files in Dbase IV.

I was wondering if anybody else has
 experienced this problem with Dbase IV.

Currently we are running a system using
Dbase IV version 2.0 for DOS.  The network
O/S that we are currently using is IBM's
Warp server.  Our file server has a 133 MHz
Pentium processor.  The standard
workstations that we use have a 100 MHz
pentium processor.

Occasionally we have several users adding
 records to our data files simultaneously.

It seems that whenever we have more than
3 people adding records to the DBFs
(notice I said adding not updating)
the MDX files get corrupted.  

We thought that by converting our system
from Dbase IV ver 1.1 to Dbase IV ver 2.0
we could correct this problem.  We are
unfortunately still having the same difficulty.


If anybody out there has any ideas on how
we can resolve this, I would be very
appreciative.

Thank you.
0
SRuli87202
Asked:
SRuli87202
  • 5
  • 2
1 Solution
 
SRuli87202Author Commented:
Edited text of question
0
 
SRuli87202Author Commented:
Edited text of question
0
 
SRuli87202Author Commented:
Edited text of question
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
SRuli87202Author Commented:
Edited text of question
0
 
cymbolicCommented:
As data is updated on these dbase systems, the index pages are sent down to the local pc's, locked on the server, updated and sent back up to be rewritten.  Often there's a whole lot more index page handling than database handling going on under the covers, that's why index pages seem to go south first.  Couple things you should look at:

1) make sure your users aren't getting frustrated and rebooting...this will honk up the best dbase app!
2) Check your app.  Make sure you always open the same files in the same order in all your apps.  This effects the order of locking and writing the index pages, and with multiple simultaneaous users, if it don't happen all in the same sequence with multiple files and index keys, somebody eventually gets stepped on!
0
 
cymbolicCommented:
Also, for the best toolset in working with dbf files and indexes, get DBFLOOK from Cymbolic Systems.  It's on AOL.COM, and in multiple shareware collections around the planet.  Then register it to get a complete system of utitlities for working with DBF's and large directories of DBF's.  You won't be sorry, I guarentee it!
0
 
SRuli87202Author Commented:
At this point in time, we are trying a new
approach to addressing this problem.  I have
made a modification to the Entry/Update
screen program so that only one user at a
time can append a new record to the datafile.
This is handled through an on error processing
routine.  So far it looks fairly prommising.
However only time will tell.  Cymbolic did give
me some things to think about though.

Thanks


0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now