Updating current information in an Access Database from outside source

I have an access database that I've imported certain information from our ERP system and it makes a new table.  Once the table is created, it runs a macro every time you start the database and appends any new records to the existing table.  Is there an easy way to create a macro that would update the existing information if something has changed in the ERP system and it sees that a record in the access database doesn't match up and needs to be updated?  For example,  their address changed from 1234 State Street to 4567 Sunny Street.
LVL 1
lrollinsIT ManagerAsked:
Who is Participating?
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Just link to the ERP tables as needed then.

Jim.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
Going field by field on every record to determine if its changed is an intensive process.  Depending on the amount of data involved, it would be faster to simply dump and re-import all the data.

  That aside, it would be far better to keep it where it is, link to the tables you need, and grab the data as needed.

  If you'd give a little more detail on # records involved, why the need for the data to be local, etc, we can give a little more direction.

Jim.
0
 
PatHartmanCommented:
No points please.  I agree with Jim.  Simply reloading the data is the better course.  I also agree that linking to the ERP is the best option but in my experience the PTB would never allow an Access app to link to THEIR data so you are stuck with an inferior option and reloading the the best of the inferior options.  When I have to do this, I always use a separate template database to hold the ERP data.  That way my own BE does not suffer from bloat caused by constant make tables or delete/insert queries.  Let me know if you want more details on this method.
0
 
lrollinsIT ManagerAuthor Commented:
ok.  That's what I thought.  I have about 100 employees and this database is for the HR person so there would be extra data in the Access database that's not in the ERP so wiping out every time isn't feasible.  Thanks for your help.
0
 
PatHartmanCommented:
I'm assuming that you are not allowed to link to the  ERP which everyone agrees is the best option.  

Therefore, keep the Access managed data in a separate table.  The only common field would be the EmployeeNum or whatever the uniqueID is in the ERP system.  Do not keep ANY field in the local Access table that exists in the ERP system except of course the link.  Keep only the locally maintained data.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.