Cannot edit subform anymore

[ranman256]

I have a basic master form/sub form.
Users could always enter data into the subform.
I added a few fields to the subform and now users cannot edit.

nothing changed...all forms are open, no locks.
the back end is a single table, no locks, no joins, dynaset.
all fields are editable, no locks, all enabled.



Why can users no longer edit? They need all these fields.
Why did it work for X fields, but not X+1 fields?

[Micron]

I hesitate to suggest the obvious for you certainly are not a novice. Since there's no query involved (as I interpret your post) I'll leave query out of the mix.
One of the new fields is a calculated field?
Table was corrupted and one or more indexes were removed (try c/r)
db is being opened read only?
Some IT guy messed with the folder permissions (playing with Active Directory?)

I would copy the db and test the copy. Then remove added fields and retest. Then put them back in one by one and retest as you go. You might find that one in particular is the culprit.

I also assumed this is an Access be and not Sql Server or the like.

[CJ_London]

I added a few fields to the subform and now users cannot edit.

if you remove those fields, can the user edit again?

all forms are open, no locks.

does that include the locked property for the subform control?

[Missinglinq]

...I'll leave query out of the mix...

Although based on a single Table...is this technically true? A lot of developers will use a Query, even though the only source is a single Table...and Access itself will sometimes employ a SQL statement, even sourcing from a single Table.

What are the properties of the Main Form? If AllowEdits is set to No, the Subform will be locked.

Linq ;0)>

[mike60smart]

I always find that deleting and recreating the form works every time.

[Micron]

Although based on a single Table...is this technically true? A lot of developers will use a Query, even though the only source is a single Table.

I'd expect someone with his experience to state that the form is based on a query if it was. As for secret Access SQL that's not the same as a query with aggregate functions and the like, which is what I had in mind.

[ranman256]

for review: no locks of any kind, a straight dynaset query on a single table , NO calculated fields.

I removed the new fields and the subform edits again.
It's like it has a limit where it can edit 27 fields, but not 28.

[mike60smart]

Hi ranman

Can you upload a zipped copy and I will see if I can replicate the problem