Great thread - thought I might chime in about using unbound controls on continuous forms.
Some background first. I have a continuous form that uses as its record source a query that is read only (cannot be updated). I want to give users the ability to update a certain field though. We'll call it textbox1.
I used an unbound text box (with a transparent background) that is placed directly over the field to be updated. We'll call this textbox2. When Textbox2 is entered, the value of textbox1 is read into textbox2. Since the two text boxes are aligned the same, have the same font, point size, and color, the user is unaware that they are editing data in an invisible text box hovering over another text box. When the user finishes editing the value in the textbox2, code associated with AfterUpdate event fires and updates the record. Finally, the form is re-queried and the updated data is displayed
Great idea, right? Wrong! As this thread discusses, values in an unbound control will repeat in the continuous form, which makes quite a mess.
However, I may have stumbled across a solution!
The key is how the controls are stacked. Place textbox2 BEHIND textbox1. (select textbox1 and format using BRING TO FRONT, or select textbox2 and format using SEND TO BACK)
-- textbox1 --
textbox1.Enabled = true
textbox1. Locked = true
sub textbox1.click => me.textbox2.setfocus
-- textbox2 --
sub textbox2.GotFocus => me.textbox2 = me.textbox1
sub textbox2.LostFocus => me.textbox2 = Null
sub textbox2.AfterUpdate => ... code to update the record, re-query form, and move focus elsewhere
When textbox1 is clicked, it updates textbox2 in the form. At this point, every textbox2 in the repeating form displays the same value. However, the only textbox2 that is visible is the textbox2 control that has focus. All the other textbox2's on the repeating form remain safely hidden behind their respective textbox1's.
Hope this helps.