- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi Robert,
Here is an idea that may be able to save you the work and
performance hit of rerunning the fill periodically and maintaining
a cache of previously returned values.
When changes are made through Access, can you define a
trigger that would insert the id of the item modified into a
changes table? You could then define a server process that would
periodically query this table for a list of changed ids since the
last execution of this process. For each changed id the process
would then query the appropriate table to get the full item and
call DataServiceTransaction.updateItem() for it?
Hope this helps,
Ed
Here is an idea that may be able to save you the work and
performance hit of rerunning the fill periodically and maintaining
a cache of previously returned values.
When changes are made through Access, can you define a
trigger that would insert the id of the item modified into a
changes table? You could then define a server process that would
periodically query this table for a list of changed ids since the
last execution of this process. For each changed id the process
would then query the appropriate table to get the full item and
call DataServiceTransaction.updateItem() for it?
Hope this helps,
Ed
Views
Replies
0 Likes
Total Likes