I know the allow additions and edits are set to yes. How do I see if my query
creates an updatable recordset? Is there some query property that has to be
set for that?
No, there is no property for that. If you open a datasheet view of your form
and see if there is a blank record at the bottom then the recordset is
updatable. If there is no blank line, it is not. Some queries create
recordsets that can't be updated. For example, Union queries, Totals
queries, and some with complex joins can't be updated.

Signature
Dave Hargis, Microsoft Access MVP
> I know the allow additions and edits are set to yes. How do I see if my query
> creates an updatable recordset? Is there some query property that has to be
[quoted text clipped - 9 lines]
> > > the form a dozen times. The tables are reasonably normalized and the queries
> > > work like a charm. This is driving up the wall. Any suggestions? Thanks!
Golfinray - 29 Feb 2008 16:01 GMT
I checked the form (actually a form and subform) both have blank records at
the bottom. The queries are plain jane select queries. Anyway, I just rebuilt
the form again and it is allowing additions and edits. Weird huh? Thanks so
much for your help! golfinray
> No, there is no property for that. If you open a datasheet view of your form
> and see if there is a blank record at the bottom then the recordset is
[quoted text clipped - 15 lines]
> > > > the form a dozen times. The tables are reasonably normalized and the queries
> > > > work like a charm. This is driving up the wall. Any suggestions? Thanks!
Klatuu - 29 Feb 2008 16:08 GMT
**** happens.
I am right now working on a similar problem. Some of my forms that were
working correctly started having problems like not being able to set focus to
a control and not being able to set a bookmark.

Signature
Dave Hargis, Microsoft Access MVP
> I checked the form (actually a form and subform) both have blank records at
> the bottom. The queries are plain jane select queries. Anyway, I just rebuilt
[quoted text clipped - 20 lines]
> > > > > the form a dozen times. The tables are reasonably normalized and the queries
> > > > > work like a charm. This is driving up the wall. Any suggestions? Thanks!