Hey Rural,
Thanks for the quick reply.
As for what I am trying to do, I was trying to get away from bound forms and bound text boxes for future databases so I can stop worrying about how to limit automatic insertion of data into tables. It seemed, after going through a lot of threads here, that standard practice seems to be to use unbound fields and make a button or other command with lines of code that inserts a new record.
As an example, if I were to make a form to fill in fields on a client profile table that has, ummm..., let's say first and last name, date of opening, monthly fee, etc. and wanted to avoid having the .mdb file create a new record automatically without all of the fileds completed because the person entering the data (generally people who are not very meticulous about that) had something else that he or she needed to attend to. I kept asking whether there was a way to stop a form from automatically creating a new record and it occured to me that after reading the threads here that the way to do it is through unbound fields. Generally, as a rule, I try to make forms that fill in one table instead of multiple tables because I gathered that that is the best way to design a database in the first place. I wanted to know if I could make a button with the code above and maybe change up the specific references to fit my database to do something like that.
It seems that what I just described above was such basic knowledge here that it would have been a bother to write up a long winded scenario (like I just did!) just to 1) annoy the generous folks here by asking a "is the sky blue" type of question (you guys are a bit tough on noobs here) and/or 2) be completey ignored. I found the thread with teh above written code after poring through the threads and that's where I find myself.
Would the folks here recommend that I use the above code for future purposes?
