Cool

Thanks to both Edhy and Trent.

That made the trick!!

------------------------------------------------------------------------
I would like to change the world, but they don´t give me the source code.
MS Windows 7 Ultimate 64-Bit
Intel(R) Core(TM)2 Quad CPU Q9300 2.50 GHz
6.00 GB of RAM, NVIDIA GeForce 9800 GT

MacBook Pro i5 OSX Lion

Edhy is right.  This is why the unique key was added back in 1.6.5 for this very reason.  By default, if you do not provide one, it will use the name of the field when you close the dialog.  But if you specify a unique value here, it will use it.  The problem is that you have the same field in there twice and they are trying to use the same key.  Provide a different key for each field and it will resolve your problem:

Hi Guillermo,

Check out the Unique Key value in the BD Search Field Criteria form.  This will allow you to have a unique key for a field which is used several times in the BD like in your case with the date range search.

Edhy Rijo

I´m trying to figure out how to implement this kind of search.



Search PO from date A to date B



Since I am looking in the same Date column field I´m getting an exception telling me that the same reference is already added to the search field collection. Do I need to override the search text manually?



Thanks

------------------------------------------------------------------------
I would like to change the world, but they don´t give me the source code.
MS Windows 7 Ultimate 64-Bit
Intel(R) Core(TM)2 Quad CPU Q9300 2.50 GHz
6.00 GB of RAM, NVIDIA GeForce 9800 GT

MacBook Pro i5 OSX Lion