clearbeforefill ?

I don't understand this behavior in the code:

I'm filling various Combo Boxes  on a form: ""BELOW IS AN EXAMPLE WHEN THE COMBO BOX gets focus:

       frmShopHandMain.txtOPTimeLine_01.Visible = True
        'TODO: This line of code loads data into the 'Database1DataSet1.LaborOps' table. You can move, or remove it, as needed.
        frmShopHandMain.Database1DataSet11.EnforceConstraints = False

Open in new window

After selecting a button on the same form "The following code gets called"
       Me.RO_InvTableAdapter1.ClearBeforeFill = False
        Me.RO_InvTableAdapter1.FillByVerifyRO_Exists(DbseRO_InvDataSet.RO_Inv, RoNum_Ln1)

Open in new window

when I set the CLEARBEFOREFILL method to "False" - EVERYTHING IS PRETTY MUCH OK for now, but
when I set the CLEARBEFOREFILL method to "True" - all of the above mentioned COMBOBOXES GET cleared out ???

the only COMMON DENOMINATOR here that I know of is the DATABASE THE THE SAME.
THE ADAPTERS, DATASETS are all different and I don't know why the form is being affected this way.???

Can anyone help me??
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris Raisin(Retired Analyst/Programmer)Commented:
How did you create your boxes? If you just copied them rather than creating a fresh box each time you may have in fact perhaps set up a group of boxes that all maintain the same properties (just a guess here). In other words, inheritance might be in play. This would be particularly true if you are creating these boxes from a library referenced within VB.Net

Try creating a fresh box each time, giving them distinct names. I can see no reason (unless you have some code somewhere that has not been mentioned) which acts when an event occurs in one box, affecting all boxes.

Chris (Australia)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MBHEY131Author Commented:
yeah,  you put me on the right track here, - I had them set up to with bindings that I had not taken into consideration the effect those bindings had on the fill query I was running - I have just tested one box and with regards to the binding behavior (of which I understand now) the code works as planned after QUERY adjustment.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.