Control Cant Be Edited; It's Bound to Expression

[AnandKhinvasara]

You were wrong in two approaches
1. Trying to edit a textbox that is linked a listbox column,which is based on a query.


2. Thinking that editing the textbox with expression, - will actually change the value in the table.

Please remember
1. query fields can't be edited, and values changed won't reflect in the table.
2. Trying to put a value in a textbox field that is not bound to a field in the table, will not change the value in the original table in any way.

Better approach
->Make a simple form that has fields bound to the table
->Have a command button on your main form that opens up form above with filter applied as below.

DoCmd.OpenForm "tblHRMSEdit", acNormal, , WhereCondition:="ItemNo=" & Me.Text209
->Make changes in the form that opens up. This will actually save the value in the table.

You can refresh the main form contraols after getting focus back, so that it reflects the values you have changed.
This can be on Close Event of tblHRMSEdit form, or on Activate/GotFocus/DatasetChage events of Main Form (you would need to play around a bit).

LEt me know if this helped. Have attached MDB with "Edit Record" button.

[AnandKhinvasara]

Other way of doing this is replacing all expression textboxes below the listbox, by a subForm linked to tblHRMS.
On Form_Load of this form, put Form.Filter = -1 so that it loads without showing any data when it first loads.

Then on click event of listbox, apply filter to this subform and requery it , so that it shows corresponding data.

This approach will work with the design that you currently have (without addition of command button), however it obviously has more work to do than previous method.

Take your best decision to get this through.

[June7]

Anand, what you suggest does not require a subform. It can be done with the single form with the edits I suggested in posts 9 and 11.

Gatsby, did you follow the suggestions? Did you remove the expressions and bind textboxes to fields? Did you change the DataEntry property to No. Did you edit the VBA code?

[gatsby]

You were wrong in two approaches
1. Trying to edit a textbox that is linked a listbox column,which is based on a query.
2. Thinking that editing the textbox with expression, - will actually change the value in the table.

Please remember
1. query fields can't be edited, and values changed won't reflect in the table.
2. Trying to put a value in a textbox field that is not bound to a field in the table, will not change the value in the original table in any way.

Better approach
->Make a simple form that has fields bound to the table
->Have a command button on your main form that opens up form above with filter applied as below.

DoCmd.OpenForm "tblHRMSEdit", acNormal, , WhereCondition:="ItemNo=" & Me.Text209
->Make changes in the form that opens up. This will actually save the value in the table.

You can refresh the main form contraols after getting focus back, so that it reflects the values you have changed.
This can be on Close Event of tblHRMSEdit form, or on Activate/GotFocus/DatasetChage events of Main Form (you would need to play around a bit).

LEt me know if this helped. Have attached MDB with "Edit Record" button.

Thanks for help AnandKhinvasara... For now, ill use this approach. if i still have time then i will revise it again. Thanks again Anand.

[gatsby]

Anand, what you suggest does not require a subform. It can be done with the single form with the edits I suggested in posts 9 and 11.

Gatsby, did you follow the suggestions? Did you remove the expressions and bind textboxes to fields? Did you change the DataEntry property to No. Did you edit the VBA code?

in my previous reply, yes i did. i set the dataentry property to NO, i tried to edit the VBA code (requery) but still no luck. im not sure if what i did was right but still not working.

[AnandKhinvasara]

June7, you are right. I missed checking that main form does not have any recordsource, so Gatsby can directly bind textboxes to fields - instead of putting a subform in future, when he decides to revamp the design.

Gatsby, welcome and glad you liked the solution. Please mark thread as solved if you have no further query.

cheers !

[gatsby]

June7, you are right. I missed checking than main form does not have any recordsource, so Gatsby can directly bound textboxes to fields - instead of putting a subform in future, when he decides to revamp the design.

Gatsby, welcome and glad you liked the solution. Please mark thread as solved if you have no further query.

cheers !

yes thanks... posted another thread in Forms. i hope its the correct category. its regarding my combo boxes.

[June7]

Oh, did I mention that you need to bind the form - set RecordSource property to the parameterized query then bind the textboxes to fields?

[AnandKhinvasara]

June7, binding to parameterized query may not work. Remember he needs to edit the field. Gatsby needs to set recordsource to Table only. Please correct me if I am wrong

[June7]

Binding to query should work just fine, as long as it is an editable query. A simple SELECT pulling only from the one table is an editable query.