Cannot enable editing of some fields

Thanks for you time and explanation! I wasn't expecting any more responses.
I will give it a shot!
Thanks Much!,
Bob

David W. Fenton wrote:
wrote in
:

I am working with a application that I did not create (Access
2007) I cannot seem to be able to allow editing of some fields on
a subform. I changed the properties to Enabled (yes) and Locked
(No); but I am still unable to edit the desired fields?

I've read all the other replies in the query. There is only one
possibility to make it editable that has not been mentioned, and
that's the Jet/ACE-only predicate DISTINCTROW. If you don't want to
dip into the SQL view and add DISTINCTROW after SELECT, go to the
query's properties sheet and select YES for the DISTINCT RECORDS
property. This predicate has the value of figuring out which rows
are unique and thus making (in some cases) both sides of a join
editable.

If it doesn't work, you're out of luck with using joins, and may
need to change your joins to subqueries using IN in the WHERE
clause, i.e.,:

WHERE ID IN (SELECT ID FROM Othertable WHERE ...)

This will leave the main table editable, but sometimes with
subqueries, Jet/ACE will not properly optimize the query and ignore
indexes on one or both sides of the criterion. However, I've found
that to be more like with NOT IN than with IN by itself.

Thanks for you time and explanation! I wasn't expecting any more responses.
I will give it a shot!
Thanks Much!,
Bob

David W. Fenton wrote:
wrote in
:

I am working with a application that I did not create (Access
2007) I cannot seem to be able to allow editing of some fields on
a subform. I changed the properties to Enabled (yes) and Locked
(No); but I am still unable to edit the desired fields?

I've read all the other replies in the query. There is only one
possibility to make it editable that has not been mentioned, and
that's the Jet/ACE-only predicate DISTINCTROW. If you don't want to
dip into the SQL view and add DISTINCTROW after SELECT, go to the
query's properties sheet and select YES for the DISTINCT RECORDS
property. This predicate has the value of figuring out which rows
are unique and thus making (in some cases) both sides of a join
editable.

If it doesn't work, you're out of luck with using joins, and may
need to change your joins to subqueries using IN in the WHERE
clause, i.e.,:

WHERE ID IN (SELECT ID FROM Othertable WHERE ...)

This will leave the main table editable, but sometimes with
subqueries, Jet/ACE will not properly optimize the query and ignore
indexes on one or both sides of the criterion. However, I've found
that to be more like with NOT IN than with IN by itself.

Thanks for you time and explanation! I wasn't expecting any more responses.
I will give it a shot!
Thanks Much!,
Bob

David W. Fenton wrote:
wrote in
:

I am working with a application that I did not create (Access
2007) I cannot seem to be able to allow editing of some fields on
a subform. I changed the properties to Enabled (yes) and Locked
(No); but I am still unable to edit the desired fields?

I've read all the other replies in the query. There is only one
possibility to make it editable that has not been mentioned, and
that's the Jet/ACE-only predicate DISTINCTROW. If you don't want to
dip into the SQL view and add DISTINCTROW after SELECT, go to the
query's properties sheet and select YES for the DISTINCT RECORDS
property. This predicate has the value of figuring out which rows
are unique and thus making (in some cases) both sides of a join
editable.

If it doesn't work, you're out of luck with using joins, and may
need to change your joins to subqueries using IN in the WHERE
clause, i.e.,:

WHERE ID IN (SELECT ID FROM Othertable WHERE ...)

This will leave the main table editable, but sometimes with
subqueries, Jet/ACE will not properly optimize the query and ignore
indexes on one or both sides of the criterion. However, I've found
that to be more like with NOT IN than with IN by itself.

Gee, I wasn't expecting any more responses.
Thanks for taking the time! I had decided that I was not going to get it
to work.
I will give it a shot.
Thanks Again,
Bob

David W. Fenton wrote:
wrote in
:

I am working with a application that I did not create (Access
2007) I cannot seem to be able to allow editing of some fields on
a subform. I changed the properties to Enabled (yes) and Locked
(No); but I am still unable to edit the desired fields?

I've read all the other replies in the query. There is only one
possibility to make it editable that has not been mentioned, and
that's the Jet/ACE-only predicate DISTINCTROW. If you don't want to
dip into the SQL view and add DISTINCTROW after SELECT, go to the
query's properties sheet and select YES for the DISTINCT RECORDS
property. This predicate has the value of figuring out which rows
are unique and thus making (in some cases) both sides of a join
editable.

If it doesn't work, you're out of luck with using joins, and may
need to change your joins to subqueries using IN in the WHERE
clause, i.e.,:

WHERE ID IN (SELECT ID FROM Othertable WHERE ...)

This will leave the main table editable, but sometimes with
subqueries, Jet/ACE will not properly optimize the query and ignore
indexes on one or both sides of the criterion. However, I've found
that to be more like with NOT IN than with IN by itself.