Now this is weird!

[stevekos07]

I must be going insane. I have a console form with links to various forms etc. I have a control button that opens a query. From this button the query opens in edit mode. Records can be edited. All good.

The query can also be opened in edit mode directly from the object list.

But if I try to open the same query from another form it opens in read-only mode. I even copied the exact macro from the one button into the on-click macro of the other button and the same thing happened. The macro actions and commands are exactly the same and the target document is exactly the same!

Am I missing something? This is doing my head in. It doesn't matter whether I open a form based on the query or even the table. The second form always opens the dataset in read-only mode.

 

[CJ_London]

what is the sql to the query?

 

[JHB]

Look at the form's properties - "Allow Edits" and "Allow Additions", are they set to "Yes"?

 

[The_Doc_Man]

If the first form is still open, then the problem may be an exclusive Open command because of it being open by another user. It would depend on options used with the Open. On the other hand, if the situation is that even with no other forms open, one form opens the query read/write and the other (separately) opens it read-only IN ISOLATION, then you have to look at the form's properties.

Though to be honest, if you are opening the query not as a sub-form of that form but just as a pop-up window from the form, the .AllowEdits property of the form should not matter.

 

[stevekos07]

Thanks The Doc Man, that seems to be the issue. It must be an Exclusive Open issue which prevents editing the records on linking from the intermediate form.

I have now deleted the intermediate form and just generated a form based on the filtered list in one step, and this seems to work ok, and is probably more user friendly as well.

Thanks!