Multiple Values in Combo Box not working

[dunc723]

Hi,

I have combo box on a form for which I want to allow multiple item selection. I have set the Allow Multiple Values property = Yes for that field in the table design. When you click the combo box on the form, it appears as a list with check boxes and OK/Cancel. When I select one or multiple items and click OK, I get an error, "Object invalid or no longer set".

I only get this error for a field that allows multiple values - if I change the Control Source in the same combo box to a field where Allow Multiple Values = No, it works fine.

I do not get the error when entering directly in the table.

If I add a new combo box and set the control source to the same field, the same thing happens. If I add a new field to the table and set to Allow Multiple Values, the same thing happens.

I have another form and table in the same database that does not have this problem. I've tried to make sure all properties in both the table design and form design are the same.

Microsoft's online help says this:

You are attempting to reference an object that is no longer valid or has not been set.

Possible causes:

• The object has been closed.
  
• The object has been orphaned (the parent object has been closed or deleted).
  
• The object is out of scope.
  
• The object library is not registered in the Microsoft Windows Registry.
  
• You are trying to reference a method or property of the collection, but you have not assigned it to a variable first.

Any ideas?

Thanks,

Pete

[orange]

I recommend that you review this and do not deal with multiple valued fields.

Here is a video (no audio) that may be useful if you decide to use MVF.

[dunc723]

Thanks, but the first article did not say anything about multi-value fields, and I am not using any lookups. I am only using a simple query to populate the value list (no problem, the right values are appearing), and only storing the actual text values selected.

While the video had a couple of useful tidbits, it still does not address my issue.

[orange]

Suggest you post a copy of the database.

Perhaps you could describe your issue in more specific terms. An example could be useful for readers.

[dunc723]

I found the problem, not related to the table design, form or control design. The database is split, and somehow the back-end table and the front-end linked table got out of sync. I was never looking at the linked table so didn't realize it was defective. I only had to refresh the linked tables in the front end and all is well.

[Micron]

Make sure you need mvf's before deciding to stick with them. Not having dealt with Access & SharePoint lists, which is about the only good reason to use them, I'm biased against their usefulness. Too often, they are used as a crutch to prop up poor db design. If you read here you could learn of some of their pitfalls. Note that Issue 1 is missing from the first result set even though there is a person involved in that record. For some, the inability to migrate a db with mvf's to other db platforms such as MySql is a big reason not to use them.