Linked form opening locked instead of disabled

[RexesOperator]

"As Uncle Gizmo has suggested, there really is no form/linked form construct in Access, other than a main form with a subform embedded in it. Calling/opening one form from another form, if that's what you're talking about, does not create a form/linked form." (quote from Missinglink)

Perhaps what is confusing here is when I said I changed the form from form/subform to form/linked form. I didn't actually change the EXISITING form. I deleted it and used the wizard to create a new form.

If there are no "linked forms" as you and Uncle Gizmo say then what is this wizard doing? (see jpeg). The second form logically behaves exactly like a subform but it is physically separated from the main form. That is what I mean by "linked form" That is the term used by Access 2003.

The first image shows the linked forms wizard and the second shows the forms I created from the wizard. The light blue form is the main form and the darker blue one is the subform. The command button Site Details is the togglelink created by the wizard.

I still need an answer to my original question - why is the subform (linked form) opening with the fields locked instead of disabled?

The first image show the linked form wizard. The second is the result. The third image shows the property settings for Enabled and locked. I hope this clarifies things.

 

[RexesOperator]

At least now I have figured out why the fields are locked - I found some code that I had not deleted when I deleted the original form (rewriting this question clued me in to that).

But I still don't understand why the fields are not disabled when the sub(linked) form is opened.

 

[gemma-the-husky]

fields will appear to be locked if the underlying record set is not updateable - perhaps thats the problem

if its not updateable- you wont get the "new record" option in the navi buttons

 

[RexesOperator]

I discovered the reason for the locking was some code that I had forgotten to delete when I deleted the form to redesign it.

The question I have now - is why don't the disabled fields show up disabled?

My other question is- how do you reference a control on a linked subform from the main form?
I tried the Me.frmName.form.subformname.control and
Forms!frmName.form.subformname.control. But of course they don't work, since the subform is not physically attached to the main form and does not have a distinct control name.

 

[boblarson]

I discovered the reason for the locking was some code that I had forgotten to delete when I deleted the form to redesign it.

The question I have now - is why don't the disabled fields show up disabled?

My other question is- how do you reference a control on a linked subform from the main form?
I tried the Me.frmName.form.subformname.control and
Forms!frmName.form.subformname.control. But of course they don't work, since the subform is not physically attached to the main form and does not have a distinct control name.

When a subform is not actually on the main form then it does become part of the forms collection just like the main form, so you can refer to it just as any other form:

Forms!YourFormName.YourControlName etc.

It doesn't require any different syntax, unlike when you have it actually in a subform container on the main form.

 

[RexesOperator]

Thanks for this ..