Importing new information into an existing table with the same structure, several records are excluded and written to Problem.DB. These records are not duplicates, nor is there any key in the original table. What other issues can cause a table to reject new entries? This is with P10. Thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Import errors
- Thread starter jlockley
- Start date
jlockley,
PROBLEMS.DB is a temporary table that Paradox/BDE creates when the records being added to a table cannot be made to fit within that table's structure.
Examples includes:
-- Alphanumerics that cannot fit within the width of the target field
-- Integer values larger than the size supported by the underlying field type, e.g. trying to place 70,000 into a smallInt field.
-- Values that do not match defined table properties, e.g. defining a lookup tale and then trying to dump a new value into the target table...one that isn't in the lookup table.
-- Trying to dump a datetime value that isn't formatted as a convertable date/time data type.
Basically, there's something in PROBLEMS.DB that doesn't fit into the original table structure.
Take a careful look at the data you're inserting and compare it--using a gimlet eye--against the target table structure. That should identify the problem. If you don't see it, please post the target table structure and an example of the data that gets thrown into PROBLEMS. Hopefuly, this will help us direct you toward the proper solution.
Hope this helps...
-- Lance
PROBLEMS.DB is a temporary table that Paradox/BDE creates when the records being added to a table cannot be made to fit within that table's structure.
Examples includes:
-- Alphanumerics that cannot fit within the width of the target field
-- Integer values larger than the size supported by the underlying field type, e.g. trying to place 70,000 into a smallInt field.
-- Values that do not match defined table properties, e.g. defining a lookup tale and then trying to dump a new value into the target table...one that isn't in the lookup table.
-- Trying to dump a datetime value that isn't formatted as a convertable date/time data type.
Basically, there's something in PROBLEMS.DB that doesn't fit into the original table structure.
Take a careful look at the data you're inserting and compare it--using a gimlet eye--against the target table structure. That should identify the problem. If you don't see it, please post the target table structure and an example of the data that gets thrown into PROBLEMS. Hopefuly, this will help us direct you toward the proper solution.
Hope this helps...
-- Lance
- Thread starter
- #3
- Status