Using Dropdowns in Search forms

syd

Help please

I want to use a dropdown in a search form for a query

The dropdown needs to contain values from a peer related table e.g.

Customer table has a field Product. I want to search for Customers with Product X.

I would like to use a dropdown on the search form of the list of products in the Product table, then select Product X from the dropdown, and display the list in a presentation.

I get the dropdown field but it is grayed out and is inactive.

Any suggestions welcome. Thanks

tford

syd,

I think that was fixed in build 1020 shown at http://www.awareim.com/changelog/

Tom

syd

Hi Tom

Thanks for the great suggestion but I tried this and still have an inactive dropdown control. May be I am still missing something

Any ideas please.

Thanks

aware_support

Are you sure the latest build does not fix the problem? It is supposed to. If you are sure please send your BSV to support@awareim.com with the description of the steps required to reproduce the problem

syd

Checked again and it does work OK. What fooled me was that the control looked inactive with a gray background and blue down arrow as against the a black down arrow on white background!

Sorry

Thanks

Syd

bartthefish

I am having a slightly different yet related problem.
I have a number of objects with search forms that contain drop-down type reference objects for use in queries originally constructed in v3.0. These queries all work very well.

However whenever I create a new query and tell it to use a form, that contains a drop-down type reference object; when the user clicks on search they get a java.lang.NullPointerException.

If I remove the drop down from the form the query works.

This makes no sense to me. perhaps I am missing something

This is on v4.7 Build 1246

tford

Hi Justin,

I see you have build 1266, but are referring to build 1246. Do you have the same result in build 1266?

I use this type of search all the time in the most recent build.

bartthefish

I have tested this and get the exact same error on build 1280.

However in my testing I redesigned the form from scratch and the problem went away. Perhaps Support could shed some light on what might have caused this.

Thanks