PRA: Exporting Nulls to Paradox Actually Exports a SpaceArticle ID: Q100964Creation Date: 01-JUL-1993 Revision Date: 19-SEP-1996
The information in this article applies to:
SYMPTOMS
No records are returned when a Paradox user tries to search a Paradox
database created using the Microsoft Access Export command. This
problem occurs only when the criteria specifies fields that are BLANK.
(The Paradox BLANK criteria is equivalent to the Microsoft Access NULL
criteria.)
CAUSE
When Microsoft Access exports a table to a Paradox database, all
fields that are NULL in Microsoft Access are replaced with a space
during export to Paradox. This prevents Paradox users from correctly
retrieving records based on the Paradox BLANK criteria command.
This problem may also occur if a Microsoft Access .MDB file attaches
a Paradox database and the Microsoft Access user deletes the entire
contents of a field from the attached Paradox database. Microsoft
Access treats the empty field as NULL, while a Paradox user treats the
same field as NOT BLANK.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Access version
1.0. This problem no longer occurs in Microsoft Access 1.1.
MORE INFORMATION
Steps to Reproduce Problem |
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.