Access should provide better query error feedback

[Guest]

When I am writing an append query for a database with several relationships,
80,000+ records, and many required fields, I don't want to get a message back
saying "Cannot append 76000 records to the database due to key violations"
especially when the query looks reasonable.

How hard would it be for Access to tell me that 30,000 records could not be
appended because duplicates values would go into a specific primary key
field?

Or instead of a cryptic validation rule violation, Access could tell me
which related table is unhappy with informaiton I'm trying to enter into a
specific field?

Or at least offer to put all problematic records into a Query Error table
for troubleshooting analysis.

The current dialogue causes hours of user frustration when the program knows
exactly why it will not accept the records.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...741ac786e0&dg=microsoft.public.access.queries

 

[David F Cox]

This is a common occurance in badly designed programs. Such messages as "bad
file name" which do not display the file name and hundreds of others. Some
are only a tad better than "Duuuh".
I mention it because none of the developers on this forum would write
applications like that ..... ( :->)

 

[Allen Browne]

Hi antrios

If it is any help, here is some more detail than is given in that dialog
about each of the possible problems it identifies:
Why can't I append some records? Trouble-shooting imports
at:
http://allenbrowne.com/casu-19.html

There really are lots of reasons why a record cannot be imported, so
hopefully that will help.