>>Sorry, not to use the *ODBC* DBase driver... To use the DBase index driver (sorry, I forget the names, as I needed the space Clipper was using on my HDD < g >).
>
>Alexandre, this will work IF Bill could compile the code (doubtful since it's a third-party product)

Ah. My writing improved, but not my reading. Sorry. Hurt me plenty. :-)))

>and IF the tables didn't have so many fields.

Jeez! I was never so wicked to use *that* many fields!

>I think this is going to be a stopping point no matter WHAT driver is used.

Maybe Bill could build and intermediate clipper app with an intermediate database...

Say, the Win app would export the data through the DBase ODBC driver into the intermediate database, and the intermediate clipper app would get the data from the DBase db (Via de NDX driver) and put it in the right place. That might even solve the field limitation problem.

That might work, no? I know it would be slow and hard disk intensive, but it probably works.

>Barbara