Linked Tables issue with some comboboxes

[west]

Hello,

I'm not sure if this is a Forms problem but since forms elements are impacted I posted it here.

I made some changes in the user interface of a spitted DB, a few combo boxes to be specific, and when I re-linked the tables the changes are not applied. I checked the master file to see if I had done something wrong and never applied the changes in the master but they are applied. I tried the splitting process a few times but same thing.

Has this happened to anyone?

-JC

 

[GinaWhipp]

Can you tell us exactly what you are seeing, i.e. missing data? error message?

 

[west]

Thanks you very much for your response, Gina.

What I don't see, is the rest of the options I included in a few combo boxes.

Ex. [Status] combo box has: "New", "Old", "Refurbished", "Decommissioned"

After re-linking the tables the new user interface has the old [Status] combo box options, only: "New", "Old".

It happens in 3 more combo boxes.

My first thought was that I might have configured those pick list options in the tables, in the look-up tab, but no, not guilty of that. I have tried locking those combo boxes, but that doesn't work.

Thanks for the help.

-JC

 

[GinaWhipp]

Hmm, okay so you added those to the Table that feeds the Combo Box, what do you see when you open the Table? Have you refreshed the links? Is this an Access backend or something else?

 

[west]

Let me explain a little further.

I have master file (integrated: front end, and test tables with test data) where all changes to the user interface are made. Then after the changes are tested and approved:

1) The master file is split again
2) The resulting back-end (tables) are stored for a short period for reference
3) The resulting front-end (user interface) is then re-linked to the production tables (back end)
4) Then the front- end is distributed to users (only after manually going to all pick list and update the ones that did not change to the new condition)

But,

In step 3 is when problem shows. Some of the pick list that has been modified as explained in post #3, are now showing a list of choices as in a previous version of the split user interface, in other words the changes are rolled back somehow.

I can still see the changes in the master file though.

Thanks for reading and helping,

-JC

 

[JHB]

Is the rowsource for the comboboxes "Table/Query"?
Is the "wrong" result still showing after the form has been closed and open again?
What if you do a "Compact & Repair"?

 

[west]

Is the rowsource for the comboboxes "Table/Query"?
Value List, I always use this option.

Is the "wrong" result still showing after the form has been closed and open again?
Yes it does.

What if you do a "Compact & Repair"?
Same, in fact I configure all my apps to Compact on Close.

... but now you have given me an idea. I don't like using the Table/Query option for my pick lists because the maintenance has to be done in the back-end, and I don't recall exactly what it was but at some point I had problems with this method. But, if I find no solution for this problem I'm gonna start using this method again. I guess I'll have to look around to see how other peoples has this Table/Query option for pick lists implemented.

-JC

 

[JHB]

Is the rowsource for the comboboxes "Table/Query"?
Value List, I always use this option.

Then do you remember to run the code which fills the valuelist when you re-link the tables?
Use the Table/Query option, it is much easier to maintain.

 

[west]

I wasn't aware of such a code. It would be nice to have it for future references.

And you're right, I just switched every pick list from Value List to Table/Query, much easier now since I just add or edit anything the users want to change in a table.

Thanks you very much JHB, oh, and if you can share that value list filler code, that would be great.

-JC

 

[JHB]

The code must be in you database, how else does the valuelist gets filled?
If I've to fill a valuelist I would use a recordset.

 

[GinaWhipp]

Value Lists are filled manually via Design Mode, that is why it's always better to use a Table or Query, especially if those values will change over time.