Never mind I figured it out. On the first epicombo for the warehouse valuechanged event, I found I could set in code for the SearchFilter value in code as folliows using VB .NET

cboFromBin_MT.SearchFilter = “WarehouseCode = ‘” & cboFromWhse_MT.Value.ToString & “‘”

Preliminary testing shows it does work.

To expand on this article:
UserCodes are a great way to populate reference fields without taking up a UD table, such as a list of defects in your product that might otherwise be a static list. You could create an epiCombo in a form customization to list defects “Burned; Stretched; Broken” as a static list, but if you add another defect class at a later date “Discolored”, you’ll have to edit all of the combo boxes you added as customizations throughout the system by going back into each one and making the change to the static list. The advantage of using the UserCodes is you can just add a new code to that group by using the User Codes task in utilities, which you can open up to responsible non-developer managers who can edit the fields at their discretion. This also allows for easy population of reporting.
In essence, you get all of the benefits of using a UD table, without actually consuming a table or having to setup additional entry forms. If your reference list becomes very large and you have a lot of other large reference lists, it would be wise to switch to a UD table.

To clarify Alex’s question:
For your purposes of populating employee names, you should not use usercodes. You are going along the correct path of pulling employee names from the EmpBasic table. Depending on how your information is setup, the employee names should be the only data pulled back from the table. There should be a property of the EpiCombo that says query on load or something to that extent, which should populate the combo on load and when you click it on typical use, it should immediately come up. If you want to add filters with a checkbox, I would use an event handler on the checkbox to both update the property of the combo and then requery its contents. If that is not your desired functionality and 3.5 seconds is too slow, I would recommend going through the index compacting procedures provided on Epicweb and possibly recommend a dump and load of the database just to enhance potential performance issues. This isn’t guaranteed to fix anything, but are just some general suggestions.

I have a need to add a dropdown box based on our Employee names and I got the EpiCombo box working…sort of. There are 132 employee records and it takes about 3.5sec once the dropdown arrow is clicked before the list populates for the user. I am adding Checkbox01 to the EmpBasic table so that I can further whittle this list down to about 85 employees. My question is how do I enter multiple SearchFilter criteria, such as EmpStatus=’A’ AND Checkbox01=TRUE?

Also, is there a way to get the list to populate quicker, or is this a symptom of connecting the EpiCombo box directly to the EmpBasic table? I didn’t see a need for using UserCodes, but if that’s what I need to do to make the code efficient, I will try that.

You set EpiBinding to OrderRel.ShortChar02. Then set EpiStaticDataList to
Fire
Water

If you want to store a code in the database vs the word fire or water use the following:
W~Water
F~Fire

Let me know if you have any other questions.