Combo box on datasheet view subform renders the subform read-only?

I have three forms within an app, and each form has an embedded datasheet view subform.

The subforms were initially designed to contain only fields, resulting directly from the underlying query, and the data contained could be edited very easily.

I then replaced two of the fields on one of the subforms with combo boxes, and now the entire subform is Read-Only. Is that to be expected? Does the presence of a combo box on a datasheet view subform disallow any editing on the entire subform?

Thanks! For your expertise and feedback!!

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Dale FyeOwner, Developing Solutions LLCCommented:
I have not tested this in an A2013 database, but generally, simply changing a control from a textbox to a combo box in a datasheet will not make the form non-updateable.

Open the query that is the RecordSource of this datasheet form and see whether the data can be edited directly in the query.  If it can, then check the datasheet form to make sure the "Allow Edits" property is "Yes".

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Changing textboxes to combos will not alter a form/subform's updateability.  Something else was changed.  Go back to your backup and start again.  Make sure you are creating the combos correctly.  You can delete the original text boxes and use the wizard to add the new combo rather than using the change feature and setting all the properties by hand.
jofoco4Author Commented:
Thanks for the direction. The problem is definitely in the underlying query structure. I removed the three combo boxes, and the (read-only) problem persisted. I then triggered the underlying query, and the resulting recordset was not updateable.

I'll hold the question open until I trace into the underlying query; I might find something in that process that would contain additional fodder for this question.

Thanks for your recommendation to "Look to the basics, Luke ... look to the basics". It was just the right touch.

jofoco4Author Commented:
Thanks to you both. After applying both of your suggestions, in an effort to isolate the point at which functionality fails, the issue has become clear. The problem is in my indexing of the support datasets, referenced in the underlying query. I've set up one of the fundamental relationships incorrectly.

I need to get that straightened out before I take another run at it, and I'm sure things will go smoother next time.

I'll close this question at the moment, and will check back in if I need further assistance. Thanks again to you both.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.