I agree -- this property is setting the TABLE as read-only, not the controls. However, in a DBEdit, you cannot type. You are in the field, you see the cursor pointer there, but you can type all you want and nothing shows up. So it's a different behavior than the combo box. I would like the combo box to behave the same way, that typing does nothing and the drop down doesn't work. But I understand that that's a function of the control, not the table.
I submitted it as a request, but a perfectly good workaround is to disable all combo boxes. Just an extra command... Karen > I would be surprised if this was not what is expected. > > The table property is making the table read only. It does > nothing to any controls on the form. I.E. It is not a control > property, but a table property. > > Thus the controls will all act as normal, except that no changes > can be saved because the table has been set as such. > > I have not tested, but I assume if you have a DB edit on your > form, it will still let you type something in it, but not save? > > Is this what you are seeing? > > > > -Bob > > > >
