Import errors table not showing validation rejections

[amteach]

having set up a table to import data with validation checks I want to show evidence of this in the form of a list of records rejected. The import errors table however does not list these even though I know that records have been rejected. The only one shown is a Type Conversion failure. I'm running 2000 at home and 2003 at work. Is there some method of switching validation capture on/off that I'm missing?

 

[willir]

Besides the records rejected due to type conversion, do you know why other records are rejected?

When I import records, I am advised of X number of records that will not be imported because of data integrity issues (for example, duplicate entries where a unique key has been defined), and the table generated with the errors will also flag other errors such as text string field truncation.

I suppose you could import the data into a raw table, and then massage teh data with code. This takes a bit of effort, and processing records via code can be slower especially if trapping errors, but it would give you what you want.

Richard

 

[amteach]

Other records rejected were due to validation checks I put in place. The task is designed to get students to evidence the fact that validation checks are trapping errors in the data imported. Errors are purposely introduced into data prior to presenting to students. The problem is that although access is correctly rejecting the errors trapped by the validation checks these are not shown in the errors table.

 

[Darrylles]

Hi,

Am I correct in thinking that you expect Access to internally report on data-validation rejection that YOU have determined?

If so, how do you expect Access to know exactly what you want to reject?

Regards.

Darrylle

Never argue with an idiot, he'll bring you down to his level - then beat you with experience. darrylles@yahoo.co.uk

 

[amteach]

This is a task set by an exam board for students. The exam board provide the data file which has known errors in it. One task for the students is to design validation checks that will trap these errors. They need to prove the validation checks work by showing the error table with the faulty data trapped. When the data file is imported Access appears to trap the errors but does not report them in the error table

 

[willir]

Hmmmm
Well not sure if this will help, but you can import the data into a new table with no restrictions (and perhaps let Access define the primary key), and then use SQL or VB procedural language to append / update the table. If you use VB procedural language, you can trap numerous types of errors and write the record number and violation to a log file or table.

 

[Lilliabeth]

I have noticed similar behavior. I don't do a lot of importing, but have noticed that the ImportErrors table seems inconsistent, but I don't use it enough to fret about it.

Darrylles, I don't understand - if Access can see the validation rule and discard instead of importing a violating record, why wouldnt it see the rule and enter a record in the Import Errors table?

Help reads like it works as amteach expects, but that's not my experience (although I admitted my exerience is limited).