I'm creating an application that will look into our ERP back end (Borland, through read-only ODBC), and find new or changed records in a specific table, then take actions, such as adding them to our google calendars, or pushing that information to a webhook for Zapier to do something with.
I'm looking to brainstorm the best way to alert myself to when these records have changed. I tried Data Macros, but they only work with Local tables. One option could be a local table, where I house only the last 100 or so records every time it closes, that I can compare the live data to, and find any differences.
I will also have a log table, where I will document every time I take action on a record. I can compare the time stamp on this to the live data, and find any new records, but it doesn't help me find any updated records.
The ERP has an alerts table, that I've used in the past to find updated records, but it relies on another application, which has proven to be buggy at times. I'd prefer to keep all this logic under my ms access roof if possible.
So, what have the experts on this forum done when faced with this type of situation?
I'm looking to brainstorm the best way to alert myself to when these records have changed. I tried Data Macros, but they only work with Local tables. One option could be a local table, where I house only the last 100 or so records every time it closes, that I can compare the live data to, and find any differences.
I will also have a log table, where I will document every time I take action on a record. I can compare the time stamp on this to the live data, and find any new records, but it doesn't help me find any updated records.
The ERP has an alerts table, that I've used in the past to find updated records, but it relies on another application, which has proven to be buggy at times. I'd prefer to keep all this logic under my ms access roof if possible.
So, what have the experts on this forum done when faced with this type of situation?