data from Paradox to Excel

[Kev SCL]

Can Excel (Office 2003) load Paradox 4x data in an XPpro environment? Data
queries set up using Excel (Office 97) in Win98 and Win95 have always worked
fine but those same queries don't run on an XPpro machine. Nor can queries
be created using the same settings even though Excel 2003 provides Paradox 4X
ODBC drivers.
Does this mean that XPpro cannot handle DOS based Paradox data? Any help
will be very much appreciated. Kevin

 

[Joseph R. Pottschmidt]

Dear Kev:

Since you are probably using an ODBC drive that was probably written
over 8 to 10 years ago, And since there isn't a 32bit equivalent unless
you upgrade to the current version of the Paradox, that you would be
hard pressed to find a better work-around for this. The reason that is
doesn't work is that it is not compatible with XPpro, and with the added
security features that the ODBC driver doesn't that into account, this
is why it is limiting your ability to run it correctly.

Hopefully, that will help you understand why it is not working.

Joe P.


-----Original Message-----
From: Kev SCL [mailto:Kev (e-mail address removed)]
Posted At: Wednesday, May 24, 2006 10:32 PM
Posted To: microsoft.public.excel.setup
Conversation: data from Paradox to Excel
Subject: data from Paradox to Excel

Can Excel (Office 2003) load Paradox 4x data in an XPpro environment?
Data
queries set up using Excel (Office 97) in Win98 and Win95 have always
worked
fine but those same queries don't run on an XPpro machine. Nor can
queries
be created using the same settings even though Excel 2003 provides
Paradox 4X
ODBC drivers.
Does this mean that XPpro cannot handle DOS based Paradox data? Any
help
will be very much appreciated. Kevin

 

[Kev SCL]

Hello Joe,

Thank you for your reply. Although it does not solve my problem it at least
gives clarity to the impression that the two products are not designed to
work together. By experimentation I have discovered that by changing the
query collating sequence from ASCII to International, the links appear to
work. I've also come to the impression that the real issue might be that
XPpro is more particular about certain things and that if I identify these I
might get a more seemless link. e.g. It doesn't like two queries from the
same paradox table in the same Excel model. This is easily worked around. I
have still to look into the issue of keyed and non-keyed fields as this also
appears to be a point of concern for XPpro. At least at this stage I have
all my many models apparently now doing what I want them to do, after having
"tweaked them". Thank you Joe for you assistance.
Regards,
Kev