Hi Barry,
with a WHERE clause like this...
Code:
WHERE dPoProd.cdPo_FK LIKE ?PARENTPKVALUE ;
AND dPoSKU.cdStatus_FK NOT LIKE 'PDCNCL' ;
AND dPoProd.cdStatus_FK NOT LIKE 'PDCNCL' ;
AND dPoSKU.lDeleteMe = 0 ;
AND dPoProd.lDeleteMe = 0 ;
ORDER BY 6 , 7
I am not seeing how a filter could work.
One suggestion: setting a filter to a JSON object with param/value pairs, to be set by the cursoradapter on the backend where the data gets processed, e.g.:
Code:
{parentpkvalue: " AH",cursku: 123456}
For reporting, we have upwards of 11 parameters that get set to filter on the various dimensions.
The filter processing would look to see if it's JSON, and if so set the params and refresh the cursoradapter on the backend (where it is available).
I can submit an ER if you want. Parameterized queries are the heart of highly-relational business apps, so something that accomplishes this in web/mobile is essential.
thanks,
Hank
Bookmarks