clearing unbound controls clears them on previous entries as well

[noamelad]

I have a form that has some unbound controls. I have created a button that will clear them when clicked (otherwise, these controls are not cleared when creating a new entry). Thing is, this button also clears the controls on previous entries. Is there a way to clear these unbound controls only for the current entry (or lock the info of previous entries so that changing them will be impossible)?

[Seth Schrock]

Because the controls are unbound, there is no connection to the records and thus Access can't allow different values in the same control. The only solution is to bind the controls to a field in a table or query.

[noamelad]

Hey Seth thanks a lot for your reply. I'm not sure exactly how to go about what I need to do. I have a form which is a questionnaire, and there is some information that I want to keep on the form but not on the table. The problem is that this information comes from people filling the questionnaire (meaning that it should change with each entry) do you know how I can go about it? If there's no way to do that, do you know where i can find out binding controls using queries?

[Rabbit]

You want to keep data, but you don't want to keep data. That doesn't make any sense. What is this data and why is it special?

[Seth Schrock]

I think that you are going to have to store the data at least temporarily in a table. You can always delete the contents of the table later. So you would just need to create a table with the same fields as are on your form and then set the form's Record Source property to the name of your table and then change each textbox's Control Source property to the appropriate field.

[noamelad]

Rabbit, thanks to you I realize now that the description I have written wasn't clear. For some reason the client wants some information to be stored only on the form entries and not in the table. In other cases I used some workarounds which meant doing things in a more messy way and using some unbound controls (for instance, rather than using a combobox to allow multiple choice, which the client said was inconvenient, I used unbound checkboxes). Anyway, for different reasons, there's some data coming from people who are filling the questionnaire, which should be saved only on their form entry and not in the database table. The problem is apparently, as Seth pointed out, that controls should be bound to allow different input for different entries.
Seth thanks again. I thought it might come to this, but that means I have built the whole thing wrong and should start over, this time splitting the form and table to make it easier to manage (as I have over 100 unbound controls). Still hope to come up wth something better, or have the client change his mind :)

[Rabbit]

I still don't understand what about this other type of data makes it so you don't want to store it in a table. You seem to be under the impression that forms can store data. Forms can not store data, they only display data that is already stored in a table. If you have two types of data, and don't want to store them in the same table, that's fine, create two tables. You can just link them to display both types of information in one form, be it with a query or with subforms.

[noamelad]

the two tables idea sounds good. how would i go about linking them with query?