Posted by eselk on 10/01/20 11:40

Thank you, and that is exactly what I found. After reading the last
post I decided to try again. This time I found that ODBC driver that
comes with Paradox (by Intersolv) and that fixed the data corruption
which I was getting with the Microsoft driver. Great!

I just started to play around with it. Most areas seem pretty fast.
The only weird thing, which I'm hoping I can find a way around, is that
it takes about 5 seconds to enter "edit mode", for example:

1. Open Linked table in Access (opens really fast, like in Paradox)

2. Browse through records (really fast), then start to edit one of the
records

.... Access hangs for about 5 seconds, then enters "edit mode"...

3. Edit the record and save it (really fast), edit aditional records
(really fast).

4. Close table, then reopen...

5. First edit has that 5 second delay again.

I'm sure it has to do with locking. In Paradox it takes less than a
second to enter edit mode (a split second), so hopefully there is a way
to get the ODBC driver to work just as fast. Not sure if it is an ODBC
thing, or Access, but I guess I could check by using some other
utilities which can use the ODBC driver (like Borland's "Database
Desktop").

I haven't brought SQL into the picture yet, but I might, for one thing
I'll only need one server license for the ODBC driver, instead of one
for each workstation if I only use Access.

Stu wrote:
> For the project I worked on integrating Paradox with SQL Server, I
> ended up buying a copy of Paradox to get the ODBC drivers that came
> with it. It was some third-party driver (and it was years ago), but
> they worked great. Of course, I wasn't doing real-time integration; it
> happened every 5 minutes or so.
>
> Not sure that helps; I tried googling for the vendor we used (I think
> it was DataDirect, but not sure). All I remember was that it was
> cheaper to get a single copy of Paradox than to get the server licence
> from the vendor.
>
> Stu

[Back to original message]