Timeline for Access write conflicts with views and insteadof triggers?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 15, 2014 at 16:17 | comment | added | Michael B |
timestamp works great actually. I already am using timestamp columns for optimistic concurrency so this solution works for me. Now access's queries use a where id=@id and timestamp_t1=@timestamp_t1 and timestamp_t2=@timestamp_t2 which is pretty good. After updating the shared access-db to hide the column and refreshing the odbc table it seems to work great.
|
|
| Sep 15, 2014 at 16:15 | vote | accept | Michael B | ||
| Sep 15, 2014 at 15:18 | comment | added | Michael B | I'm not an access expert how can I set up triggers in access? | |
| Sep 13, 2014 at 13:45 | history | edited | Hannah Vernon♦ | CC BY-SA 3.0 |
added 194 characters in body
|
| Sep 13, 2014 at 0:17 | history | answered | Hannah Vernon♦ | CC BY-SA 3.0 |