D
Dave
Hi!
I am writing an application that needs to provide a way for users to query a
database, by filling out a form of fields and values - i.e. QBE (Query By
Example).
I'm playing with different ideas as to how to best provide a UI to do this.
The main idea I'm working with now is to use the .NET PropertyGrid control.
It would contain the different fields that people could query on, and people
could fill out the value column with the values they want to query. There's
a lot to like about PropertyGrid for what I'm trying to do. It would
support complex values, with more than one "property" as part of a single
value. It would support editing of values of different data types. It
allows for grouping properties together. Etc.
My question is - is this reasonable to attempt? The problem is that I don't
really have an object whose "properties" are being edited by the
PropertyGrid control. Rather, I want to be able to dynamically,
programatically, populate the propertygrid control myself. I like the UI of
the PropertyGrid control, but I'm not sure if I'm shoehorning it to provide
functionality that's so different from what it was intended for, that it
isn't worth doing.
Does this seem reasonable? If so, can anyone point me to some sample code
for filling out a PropertyGrid programatically? If not, does anyone have
any better suggestions for providing a QBE UI?
Thanks!
- Dave
I am writing an application that needs to provide a way for users to query a
database, by filling out a form of fields and values - i.e. QBE (Query By
Example).
I'm playing with different ideas as to how to best provide a UI to do this.
The main idea I'm working with now is to use the .NET PropertyGrid control.
It would contain the different fields that people could query on, and people
could fill out the value column with the values they want to query. There's
a lot to like about PropertyGrid for what I'm trying to do. It would
support complex values, with more than one "property" as part of a single
value. It would support editing of values of different data types. It
allows for grouping properties together. Etc.
My question is - is this reasonable to attempt? The problem is that I don't
really have an object whose "properties" are being edited by the
PropertyGrid control. Rather, I want to be able to dynamically,
programatically, populate the propertygrid control myself. I like the UI of
the PropertyGrid control, but I'm not sure if I'm shoehorning it to provide
functionality that's so different from what it was intended for, that it
isn't worth doing.
Does this seem reasonable? If so, can anyone point me to some sample code
for filling out a PropertyGrid programatically? If not, does anyone have
any better suggestions for providing a QBE UI?
Thanks!
- Dave