I've got an old DOS Paradox database that I can't get rid of. We have
way to many scripts and forms to convert everything at once. Instead
we would like to be able to access the Paradox data from MS Access, so
that we can create a few select forms using Access.
I've been trying for a while to get MS Access to work correctly with a
linked Paradox table. It works fine for reading, but when I attempt to
edit records in Access, especially if another user is working with the
same table in Paradox at the same time, I end up with data corruption.
I've read all of the articles and tried all of the fixes, including
getting the latest versions of the BDE and all of the MS Access and
MDAC updates, but no luck.
Has anyone done something like this, or faced a similar problem? I
also looked at the newer version of Paradox, which works fine
side-by-side with the old version, but it is not anywhere as nice as
Access (I actually prefer the old DOS version over the new Windows
version of Paradox).
Would adding a SQL server as a middle-man between Paradox and MS Access
help? Can a SQL server serve Paradox tables without the corruption
issues I'm having with MS Access?
I know the BDE is able to work with my Paradox data, without causing
data corruption, because I can write a program using BDE components
(VCL, Delphi, C++) that work with the data. However, I'd rather use a
database program like MS Access, which already has all of the nice
query building and report functions, as it would take much less time
than creating an application in Delphi, C++, Visual Basic, etc.
