Checking for errors in spreadsheet to be imported to a table

[kjharve]

Hi,

I am setting up a database for the company I work for. The database will be fed information from various departments. Each of these departments will have to populate spreadsheets. Some will be done manually, others by existing computer systems.

Potentially there could be errors in the spreadsheets, there might be typographical errors, duplicate records or key violations etc. As far as I can see I have a few options:

1.) Use the TransferSpreadsheet function and let Access worry about errors but risk some data not being transferred.

2.) Write the data to a temporary table first and then check each record before writing it to the actual table.

3.) Write some code in Excel VBA which uses ADO to check for errors in the spreadsheet so that when it is imported I can be confident no errors exist.

What method is generally employed in this situation? And are there any pitfalls I need to be aware of?

Advice appreciated!

PS - Sorry for the "essay-style" question!

 

[MyBoo]

Being that you can't know ahead of time what types of errors will be found, I would use essay entry #2 first. This would allow me to at least see what I'm up against. I would make a report of errors and report them to each dept head to see if there were some sort of action plan that could be implemented at that level (most probably not). Based on my findings, I may find it easier to write VBA against the temporary table.

I don't think essay entry #1 is a good solution... #2, then #3 is the way to go. IMHO

 

[kjharve]

You're right, #1 is definitely the least preferred. I would need to rely on the database user to correct errors and re-import any data that got left out - not likely to happen.

The only thing that puts me off writing to a temporary table is that my Excel VBA skills are far better than my knowledge of Access.

 

[MyBoo]

Well, then being that you're more comfortable with VBA in Excel, I'd go through door #3 then.

Although, I think you would get more out of VBA for Access... my opinion... and what you know in Excel VB, can quickly and easily be transported to Access VBA. Little differnces, but the concepts are exactly the same.

 

[Norie]

Kev

Why not eliminate the errors in the spreadsheets by using things like Data>Validation...?