Yes. It's called developing forms using a technique called "Unbound Forms". It basically means all the fields are "unbound" (ie. the form doesn't have a recordsource and all the fields on the form have no sourceobject - ie. empty shell so to speak). You then write vba code when the user clicks the "Save" button to open a recordset in code and write the values from the form into the recordset.
It is the ideal method of coding forms as you don't have a constant connection to the backend tables and it's very quick for users with slow computers/connections. It does take a little bit longer developing this way as you have to do a lot more coding than you would on a bound form but it's well worth it especially on extremely large datasets.
You'll want to have functions and call them. The functions are like those you were taught in computer classes (for example, 1 function to write/update (save) the date in the recordset from the form entries, 1 function to retrieve the data from the recordset and then display it to the form, and 1 function to delete the recordset from the ID passed to it that's on the form (you'll actually want to utilize the ID (autonumber or Primary Key) in almost all the functions to construct your vba SQL statement in order to return/update when calling those functions. Then you simply code your appropriate buttons to call the necessary functions. (make sure to put in code to question the user if they should close the form without saving their updates.)
Another method is to write to a "temporary" type table first and then run a query to append that record to the main data table (and then delete the info in the temp table) but this can be problematic if you have multiple users in the same mdb file (you'd need to clone your source mdb file so each user is in their own mdb file or you'll need to identify which record in the temp table is that specific users.) I wouldn't necessariy recommend this method and would highly recommend using the unbound forms technqiue. Unbound forms is a great practice technique for writing code against extremely large datasets (the forms will open very quickly) if you haven't done them already. There are several posts in this forum you can do a search for on the topic (ie. unbound forms) to find out more info.
There might also be a few other techniques you can use without using unbound forms which other posters might be able to suggest.
Last edited by pkstormy; 05-23-09 at 04:19.
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)