Not sure I'd call this a 'deficiency' of split form! The primary purpose of this new (in 2007/2010) feature is to allow you to use the Datasheet portion of the Form to quickly locate a Record, and then use the Form portion to easily View or Edit the Record. Previously, to have this kind of functionality, and it is something developers/users frequently wanted, you'd have to
- Display all Records in a Datasheet View Form
- Grab the Primary Field of the Current Record
- Write code to open a second, Single View Form, to the Record that matches the PK
- Do whatever to the selected Record
- Close the secondary Form
- Return to the Datasheet View Form
Now, all you have to do for this functionality, is to set the Default View Property of the Form to Split Form. If used for the purpose that it was developed for, it's not deficient at all!
If you want to prevent the error, i.e. keep users from utilizing the Combobox while on the Datasheet portion of the Form, the only thing I can think of is to set the Split Form Datasheet Property from Allow Edits to Read Only.
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007