Form edit to specific record and not all records

[ShandiraP]

I need assistance on how to update a form for a specific record. What is happening is I update one record and all of the records in the form/table update for that field. They are all unbound boxes. Some are drop-down and linked to other tables. Some are check boxes. How can I update the one record without updating all of them?

My thought is to bound it but I want to bound it to the record and not to another table or list. Anyone? Anyone??

 

[Beetle]

They are all unbound boxes

Then there is nothing to "update" (i.e. nowhere to save the value).

My thought is to bound it but I want to bound it to the record and not to another table or list. Anyone? Anyone??

Is there some reason why these controls are not already bound to a field?

More specifics please.

 

[ShandiraP]

The specific box I am currently testing is an unbound Combo Box using a Table List to select options from. The table has the selections I want but only want to apply to each record individually. If I select option 1 - all of the records change which is what I am trying to prevent from occurring.

 

[VilaRestal]

It would be best to upload your database so we can see exactly what's going on. Maybe chat a bit to get your posts over 10 so you can.

Almost without any doubt you do want to be binding your controls. Only in quite extreme circumstances would that not suffice. But there is a chance that this combobox's value doesn't represent a field in your table.

I expect you're not understanding what binding a combobox means. It doesn't bind it to its row source (the list it shows) in any way, it binds the value you select in it to a field in the current record.

But maybe it's more complex than that and I think you'll struggle to explain properly as we will. Uploading a copy of the database would be best.

 

[ShandiraP]

If anyone else understands the situation, it would be greatly appreciated if you can help. I explained the situation as it is. The selections are not part of the same table as the rest of the information on the form, therefore it is not bound to the same table. I am inserting a combobox that is related to the control source of the form. I am very familiar with Access and know this is a tricky process because I am not just using one table for all of the selections. I think because of it being so complicated, it sounds confusing. Thanks Beetle for trying!!

 

[VilaRestal]

Sorry Shandira, you haven't explained:

The table has the selections I want but only want to apply to each record individually. If I select option 1 - all of the records change which is what I am trying to prevent from occurring.

What do you mean by 'apply to each record'?

It sounds like it represents the value of a field so should be bound. It sounds very straightforward. And knowing that an unbound control will not 'apply' in any way to the current record (without VBA code in the current event and/or update events) is quite basic for someone very familiar with Access.

 

[ShandiraP]

I am creating-editing a Form - there are bound controls that are directly related to a table. I am trying to determine how to update an Unbound ComboBox that I have directly reading to a Control Source in another table. I am not using a field in the original table because the field I am adding would ruin the integrity of the original table. I can pull the results in a database or report using a query, however, I am trying to allow edits and simple updates using a form. I want that while in the Form as I update it, it updates only the one related record in the form and not all of the 723 records in the form. If it is a VBA coding, then if you know, what is the coding to have a combobox perform the result? This is what I am asking for help on if I can. I have exhausted my search throughout help pages and forums.

 

[Beetle]

So the table (or query) that is the record source of your form is in no way related to (and therefore does not have a foreign key field in which to store a value) the table that your combo box is based on?

For example, an Invoice table would have a relationship with an Items table via a foreign key field like ItemID. A form based on the invoice table might have a combo box where a user would select items to be sold on the invoice. The Control Source of that combo box would be the FK field (ItemID) from the invoice table, but the Row Source would select the ItemID and ItemName from the Items table. When a selection is made, the appropriate ItemID is then stored in the Invoice table.

If you are saying that the above scenario does not apply to your situation, then that brings us back to the problem of having nowhere to store the selected value and no way to solve the issue.

 

[VilaRestal]

If you're absolutely certain that this combobox cannot be bound to a field then:

You will need code that sets it's value and possibly rowsource in the form's current event.

You will also probably need code in the combobox's after update event that 'applies' its value to the current record.

Without knowing lots of details (names of tables, names of fields and their data types, names of controls, what it's supposed to do, etc) I can't hope to help you anymore than that.

Uploading the database would be the easiest way to communicate those details.

 

[ShandiraP]

Ok Pat. So I have to somehow find a way to bind the control to a field in the form's RecordSource. I am selecting a specific table for the record source but that isn't working on binding the control. Do you have any suggestions on how this is done?

 

[Beetle]

I am trying to determine how to update an Unbound ComboBox that I have directly reading to a Control Source in another table. I am not using a field in the original table because the field I am adding would ruin the integrity of the original table.

Why do you think that having a foreign key field in the table would "ruin the integrity" of it?

I'm not saying it would or wouldn't, but it's hard to offer advice when we don't know why you're doing what you're doing. If circumstances dictate that each record in one table should store (i.e. relate to) a value from another table then there should be a FK field. What are we missing?