Combo Box in .accde file picking up values not in row source of table

[Gutbarger]

Hi there,



I hope someone can help. I've inherited a database at work which someone has attempted to modify and which is now causing me problems. Basically the database is split, and the front end has been saved as an .laccdb file. At some point in the past someone has managed to amend a combo box in the front end and add more options to the list it shows. However I don't know how they have done this because, if I look at the data table which contains the row source, the two don't match up.

Combo box in front end: Name A, Name B, Name C, Name D, Name E
Row source in table: Name A, Name B, Name C

I thought that .laccdb files were locked yet somehow the combo box in the form has been edited with these extra options. If I take a local, older version, of the front end (which is still linked to the table) the changes to the row source reflect in the forms so it's almost as if the link between the combo box and the row source has been broken and the extra names coded in somehow.

I hope this doesn't sound too vague but I don't know how to make the combo box pick up the correct values. If anyone can shed some light it would be appreciated.

Thanks

[Bob Fitz]

I thought that .laccdb files were locked yet somehow the combo box in the form has been edited with these extra options.

See: http://file.org/extension/laccdb
If you want to prevent users from being able to make changes to the design elements you would need to give each user a copy of the front end db as an .accde type file. Make sure you keep a copy of the original .accdb in case you need to made changes to the design in the future.

[Gutbarger]

Hi Bob,

Thanks for the reply. I'm sorry if I didn't explain myself properly, but the problem I have is that someone has been able to amend the combo box list despite the database being split, and a .laccdb file created. In doing so the link between the row source and the combo box appears to have been broken. I need to know how the amendment was made. Any ideas?

[Bob Fitz]

the problem I have is that someone has been able to amend the combo box list despite the database being split

Splitting the db will not prevent this. See my original post.

and a .laccdb file created

This file is created by Access when the backend is connected to. Did you not read the link I gave you.

the link between the row source and the combo box appears to have been broken.

I have no idea what this means.
What is the Row Source setting of the combo box.

[Gutbarger]

Apologies, I didn't mean .laccdb. I posted this question too early in the morning !

I have a split database, with a back end and a front end which is an .accde file, and which is shared amongst users. I understand that the .accde file is locked and the forms, queries etc within cannot be amended. I have a combo box in a form with the values:


I have found a field in the one of the tables which should provide the data:

The two contain different entries, and changes I make in the row source do not reflect in the combo box. I have checked and there is nowhere else I can see from where the data in the combo box should be populated. I didn't think it was possible to change an .accde file but it looks like someone has managed it, and it doing so dissociated the combo box in the form from its data source. Is this possible? Can it be fixed? I have spent a few hours on the internet and looked in reference books but I am stumped, so any help would be appreciated.

[aytee111]

Did you recreate the accde file from the database that is working correctly? It may be based on a prior accdb.

[Gutbarger]

Thanks for the suggestion. I'll give that a go but the copy of the accdb which is available is missing some references to, I think, Adobe plugins. I'll have to sort that out before I can convert to accde as it is erroring at the moment.