Feb 20, 2012
I have a tab control application, each tab loads a particular user control and each of those user controls will then add other user controls that are used amongst other the user controls. For example, I have an "ucQuotes" page and an "ucInventory" page, when the specific tab is selected, the "uc****" user control is loaded on that page, and in the case of "ucQuotes" and "ucInventory" they both use a control called "ucPartNumber"; a user control consisting of a combobox, textbox, and button. I have no issues reusing the shared user controls, in this case. My problem arises with my "ucQuickPrice" control, as it is always present at the bottom of the tab control form (separate from the tabcontrol, but on the same form), and it too uses ucPartnumber.
View 2 Replies
Here's my issue, as I type into the ucPartnumber combobox, the text I type does not appear in the combobox, it appears in the textbox of the ucPartnumber control that is being used on the tabcontrol page. There are no shared instances of ucPartNumber, nor do I have this issue between typing on one tab page and the text showing on the user control of another tab page.I tried just creating the ucPartNumber controls on the ucQuickPrice control, not adding a new instance of ucPartnumber on the .Load event, and the issue persists.
The combobox(s) in question are bound programmatically with about 40,000 items, ".datasource = dataset.tablename" not to a bindingsource. Autocomplete is set to none, I added code to utilize tool tips and the basic combobox filtering functionality. Is this a bug, or is there something I'm neglecting? I'm about 95% complete with this application, and this just happened today. I made the decision, to just reuse the ucPartNumber control on the ucQuickPrice control (originallly it's size and orientation would not fit, but I added some coding to detect what parent is adding ucPartNumber and to change its appearance accordingly). Before, I made this change, I did not have this problem. And, in trying to go back to how I had things set up before the change, the problem will not go away. if the whole control within a control verbage I used is a bit confusing, let me know and I'll try to better explain what is happening. At this point, I'm going to close and reopen vbexpress, as when I started this ordeal, vb started acting weird and wanted me to save all my work, it usually does this before locking up.