B
box2003
Hello,
I am running two queries, a query that will find duplicate rows in a main
table and one that will delete duplicate rows in a main table. When I run
my duplicates query to find duplicates, I am able to identify the
duplicates. When I run my duplicates maintenance procedure, to delete
duplicates on the same main table, the below message appears.
"The field is too small to accept the amount of data you attempted to add.
Try inserting or pasting less data."
Here is the problem, on my test dataset of 1000 records, selected from the
same main table, both procedures complete successfully. When I run the
procedure on live data of 120,000 records, from the main table, I can find
the duplicates. When I run the delete duplicates query, the above message
appears.
The table for which this duplicate procedure runs against in a live
environment is large by rows and and columns. How would someone suggest
identifying the field of data that may be causing the above message. I have
been able to identify some of the potential cause by examination of the raw
data, though I have not completely corrected the problem. Is there a faster
or more effecient way?
Thank you.
I am running two queries, a query that will find duplicate rows in a main
table and one that will delete duplicate rows in a main table. When I run
my duplicates query to find duplicates, I am able to identify the
duplicates. When I run my duplicates maintenance procedure, to delete
duplicates on the same main table, the below message appears.
"The field is too small to accept the amount of data you attempted to add.
Try inserting or pasting less data."
Here is the problem, on my test dataset of 1000 records, selected from the
same main table, both procedures complete successfully. When I run the
procedure on live data of 120,000 records, from the main table, I can find
the duplicates. When I run the delete duplicates query, the above message
appears.
The table for which this duplicate procedure runs against in a live
environment is large by rows and and columns. How would someone suggest
identifying the field of data that may be causing the above message. I have
been able to identify some of the potential cause by examination of the raw
data, though I have not completely corrected the problem. Is there a faster
or more effecient way?
Thank you.