Most of the impact on performance will depend on the type of DB you use (Acces vs SQL - big difference in what they can handle), and whether the app is a desktop app or multi-user. If it´s a desktop app, you can probably take the chance to update every time the user changes data. However, I would reccommend that you build a class module that can handle the data and then save it all at once to the DB (unless there's a very good reason not to do this), in any event, if you want to synchronize the data for other users to see it, it will be hard, since you would still be locking the record while writing to it, thus preventing other users from reading its updated contents. The class solution is much better, I think, since you can provide the user with a "Cancel" option in case they wish to do so, otherwise, you've already lost the original data.
|