This is a known issue Pat. All the actions on a table that require a “requery” should be disabled when there are unsaved changes present on the model. Don’t want you losing those changes…
Pretty sure that will be fixed in the next release.
This is a known issue Pat. All the actions on a table that require a “requery” should be disabled when there are unsaved changes present on the model. Don’t want you losing those changes…
Pretty sure that will be fixed in the next release.
