By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,054 Members | 1,304 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,054 IT Pros & Developers. It's quick & easy.

Synchronized combo boxes, dependent field not showing all options after migration of data

P: n/a
I have an order entry database with two forms. One is for new orders
the other is to update orders. The forms are identical except that one
is strictly order entry. On both forms are three sets of sychronized
combo boxes. When entering test data everything worked perfectly. I
recently migrated 5,000+ records from an Excel file to the database.
The migration was successful and all records were copied over. When I
checked the underlying table, all information was as it should be. But,
when I go to the update order form, on two of the dependent combo boxes
only some of the items are showing. For example, one set of combo boxes
is for order type and features. If the order type is "disconnect" then
its assocated feature correctly appears, if the order type is "change,"
it does not, although the data is in the underlying table. If I prnt
out a record, everything prints correctly and all missing data is
there. Does anyone have any idea why the dependent combo box options
are not always appearing?

Aug 17 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
are you forcing a requery of the second combobox when the first is
changed?
and why do you have two identical forms? Why not just set the
allowEdits property of the form when you open it?

Aug 17 '06 #2

P: n/a

pi********@hotmail.com wrote:
are you forcing a requery of the second combobox when the first is
changed?
and why do you have two identical forms? Why not just set the
allowEdits property of the form when you open it?
Thank you for your message. In answer to your two questions: 1) Yes,
the problem is not with the combo boxes working. It is with the boxes
showing the data after the importation of records; 2) the reason for
the two forms was at the request of the end-users. Are you suggesting
that to reduce it to one form would elimate the problem?

Miguel

Aug 17 '06 #3

P: n/a
What's the practical difference between opening a form as read-only and
creating a second form that's read-only? Just more stuff.

Aug 17 '06 #4

P: n/a

pi********@hotmail.com wrote:
What's the practical difference between opening a form as read-only and
creating a second form that's read-only? Just more stuff.
I do not understand your question. Where did you infer that they were
read only. One is for data entry and one is for updating orders. Read
only would allow for neither, now would it.

Aug 17 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.