S
slonocode
I have a situation where I have read only access to an Access database.
I need to query the database and insert the rows retrieved into my own
database. However there is no gaurantee that the original query won't
return rows that I've already inserted into my own database.
So my question is what is the best way to handle the situation? Just
trap the errors when the insert fails? Query my own database for
primary keys and then discard those rows from the original query? Check
each row of the original query for existance in my own database before
attempting to insert?
This is a desktop application which is basically single user so
performance isn't of the utmost priority. I'm basically looking for a
best practice approach to this problem.
Thanks
Slonocode
I need to query the database and insert the rows retrieved into my own
database. However there is no gaurantee that the original query won't
return rows that I've already inserted into my own database.
So my question is what is the best way to handle the situation? Just
trap the errors when the insert fails? Query my own database for
primary keys and then discard those rows from the original query? Check
each row of the original query for existance in my own database before
attempting to insert?
This is a desktop application which is basically single user so
performance isn't of the utmost priority. I'm basically looking for a
best practice approach to this problem.
Thanks
Slonocode