I actually use a similar item already for an app the is user definable and settings are mobile. With our case we have a file assigned by user id that holds the data. What we do is check for the file and if found get a date we have in it for last change. Then we attach to the database and compare the last change on the server table. If they are a match we do nothing more except use these files to populate various controls on the app. Since these apps are for dealing with reps under them they are static to that user. When they add someone we add it to their local file and send to the server and update the last. When they close the app we drop everything. If for whatever reason they go to another desk the same thing happens. Now if the file is not found or the last change don't match we refresh then. This saved us a lot unneccessary network time that using from the database itself was eating up. Plus we reduced overall query needs. All in all good article.