Winform Front end SQL/Query Builder for end user options

[dv2020]

Hi All,

I'm currently exploring options to provide a front end user to query a database tables by selection which items/filters they want. I came across this product EasyQuery which looks promising. My initial though was simply to use a data grid/or traditional report and then have the user select check box's, or multi combo select and it will write out the SQL query in a string, run the query against the DB and return the result.

I'm keen to see, if anyone has done something similar, or has any other ideas of what is worth exploring and trying.

Thanks

Regards

dv

 

[Skydiver]

My two cents: The issue with most modern query builders is that they are just visual ways of building a SQL query. This still requires the user to have a programmer mindset. They still have to know how to build the query on a conceptual level -- all the query builder is doing is taking care of the syntax, keeping track of AND/OR nestings, and if the query builder is good, table JOINs. This may help a business user with an Information Systems background, but not typical business user who's day job is being a dentist, carpenter, or doctor.

Back in the late 80's and early 90's, Borland's Paradox database had what they called "query by example". The UI guided the user to get the query they wanted by letting the user do the filtering themselves visually. To me, this is what a typical business user would find more useful.

Under the covers, Paradox would build the SQL query and make it available if needed even more tweaking.

(I only tinkered with it a little bit because even back then, I was NoSQL guy even before NoSQL was a thing. At that time, I called myself anti relational database.)

I can't find a direct link to Borland's original DOS version with screenshots, but this link should you give you a feel for how it works with the screenshots from the old Windows version of Paradox:

Paradox

 

[dv2020]

My two cents: The issue with most modern query builders is that they are just visual ways of building a SQL query. This still requires the user to have a programmer mindset. They still have to know how to build the query on a conceptual level -- all the query builder is doing is taking care of the syntax, keeping track of AND/OR nestings, and if the query builder is good, table JOINs. This may help a business user with an Information Systems background, but not typical business user who's day job is being a dentist, carpenter, or doctor.

Back in the late 80's and early 90's, Borland's Paradox database had what they called "query by example". The UI guided the user to get the query they wanted by letting the user do the filtering themselves visually. To me, this is what a typical business user would find more useful.

Under the covers, Paradox would build the SQL query and make it available if needed even more tweaking.

(I only tinkered with it a little bit because even back then, I was NoSQL guy even before NoSQL was a thing. At that time, I called myself anti relational database.)

I can't find a direct link to Borland's original DOS version with screenshots, but this link should you give you a feel for how it works with the screenshots from the old Windows version of Paradox:

Paradox

Thanks for the reply.

Will look more into this. I feel the best solution long term would be to head down the path of creating the query builder from scratch, as could simply what would be required to allow for basic users to select which Attributes they would want to include in the query.

 

[dv2020]

Hi All,

For anyone who visits this page and is looking for nice solution that allows end user so safely create there own basic queries against a database, i setup EasyQuery: .NET/ASP.NET query builder and advanced search components (korzh.com) within a few hours, the trial version is the full version for 60 days which is great to try. Most functions are there, and allowed me to create a nice interface inside a winform, where users can create base queries against a DB.

It does work well, the documentation is a little thin, but the ticket support system is great and the creator responds quickly.

Thanks

David