Custom Field Properties binding best practices???


Author
Message
Edhy Rijo
E
StrataFrame VIP (4.6K reputation)StrataFrame VIP (4.6K reputation)StrataFrame VIP (4.6K reputation)StrataFrame VIP (4.6K reputation)StrataFrame VIP (4.6K reputation)StrataFrame VIP (4.6K reputation)StrataFrame VIP (4.6K reputation)StrataFrame VIP (4.6K reputation)StrataFrame VIP (4.6K reputation)
Group: StrataFrame Users
Posts: 2.4K, Visits: 23K
Hi Ben, Trent and all.
I am working on a form that will be use to capture the parameter values to generate a query for reports.  In this case we are talking about multiple parameters, at least 20 or more.  These parameters will be capture in all type of controls, like Textboxes, comboboxes, checkboxes, etc.

My questions is what would be the best way to bind those parameter controls so it will be easier to maintain and also to access their values and enforce testing rules?

Since SF binding requires a business object, I was thinking on creating a  SQL view with all the fields I would use as a parameters and then create a business object and maintain it with the BOM as normally done, but then to be able to capture any parameters value in the form, I would need to add a record to that BO and then make sure it is discarded bo.Clear() or something like that, to avoid trying to commit anything back to the database.

Is there any better approach to this?

Main goal is to make this form easier to maintain when adding more parameters as needed, and avoid having to create a whole bunch of custom field properties and manually link or bind them to the controls value.

As always, any input, suggestion is greatly appreciated.

Edhy Rijo

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search