Instead, a typical Access database is a a collection of tables, plus a set of objects built around those tables — forms, reports, queries, and so on.
In addition, those objects must adhere to a set of design principles or the database will either work poorly or fail altogether.
Edit: Findings of Dakusan prove that my performance estimations are not quite valid.
Please see this answer for another, more elaborate research.
Some references: I think you should check the following project at This sample application is developed in C# as a library with the project name “Auto Updater”.
So in general, I feel the INSERT method is both best and easiest to use.
The queries are smaller and easier to read and only take up 1 query of action. Bonus stuff: The solution for the INSERT non-default-field problem is to temporarily turn off the relevant SQL modes: first if you plan on reverting it. SQL files to remove php interpreter overhead There is a setting you can alter called 'multi statement' that disables My SQL's 'safety mechanism' implemented to prevent (more than one) injection command.
Microsoft Office Access 2007 provides a number of tools for updating existing records, including datasheets, forms, queries, find-and-replace, and the new Data Collection feature.
As you proceed, remember that updating data is not the same process as entering new data.