Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General Discussion » View Thread |
Messages 1 to 8 of 8 total |
what's in a name? |
Thu, May 24 2007 3:19 AM | Permanent Link |
"Harry de Boer" | LS
My boss asked me an interesting question: can we make one of our apps in a way that the tablenames and fields get descriptions that we want. We can already do that (using TsiLang) with UI controls, but when we deliver a end-user report mechanism where a customer could query the database himself then the table- and fieldnames are the one as we named (designed) them. What we want is that a customer also sees the proper desriptions there. It is not only for different languages we want this, but also for different vertical markets where for instance a table should be called 'Campaign' one time, and 'Project' another time. Is there a querybuilder and reportbuilder that would support this (and can use EDB), or are there other solutions or ways to get this going the way we want to? Regards, Harry |
Thu, May 24 2007 4:55 AM | Permanent Link |
I'm fairly sure that ReportBuilder allowed this - I've stopped using it
though. The "end user name" was a property of the report link. /Matthew Jones/ | |
Thu, May 24 2007 10:18 AM | Permanent Link |
"Kim Madsen" | Hi,
You could create localized views of your tables. Then let the user operate against the view. The actual datastorage is made in the table, but the 'interface' to the user is the view. -- best regards Kim Madsen kbm@components4developers.com www.components4developers.com www.myc4d.com - Your access to cool code The best components for the best developers Application server enabling technology for developers "Harry de Boer" <harry@staaf.nl> skrev i en meddelelse news:554ACED0-5172-4D85-AFB6-E91D337A44D2@news.elevatesoft.com... > LS > > My boss asked me an interesting question: can we make one of our apps in a > way that the tablenames and fields get descriptions that we want. We can > already do that (using TsiLang) with UI controls, but when we deliver a > end-user report mechanism where a customer could query the database > himself > then the table- and fieldnames are the one as we named (designed) them. > What > we want is that a customer also sees the proper desriptions there. It is > not > only for different languages we want this, but also for different vertical > markets where for instance a table should be called 'Campaign' one time, > and > 'Project' another time. > > Is there a querybuilder and reportbuilder that would support this (and can > use EDB), or are there other solutions or ways to get this going the way > we > want to? > > Regards, Harry > > |
Thu, May 24 2007 12:00 PM | Permanent Link |
"Harry de Boer" | Kim,
That's an interesting thought. Thanks! PS: any progress on EDB support for the 2.7 kbmMW release (will it be in there) for June? Regards, Harry "Kim Madsen" <kbm@components4developers.com> schreef in bericht news:FF0320D5-9214-4155-B581-ADAB6FB91C5B@news.elevatesoft.com... > Hi, > > You could create localized views of your tables. > Then let the user operate against the view. > The actual datastorage is made in the table, but the 'interface' to the user > is the view. > > > -- > > best regards > Kim Madsen > kbm@components4developers.com > www.components4developers.com > > www.myc4d.com - Your access to cool code > > The best components for the best developers > Application server enabling technology for developers > > "Harry de Boer" <harry@staaf.nl> skrev i en meddelelse > news:554ACED0-5172-4D85-AFB6-E91D337A44D2@news.elevatesoft.com... > > LS > > > > My boss asked me an interesting question: can we make one of our apps in a > > way that the tablenames and fields get descriptions that we want. We can > > already do that (using TsiLang) with UI controls, but when we deliver a > > end-user report mechanism where a customer could query the database > > himself > > then the table- and fieldnames are the one as we named (designed) them. > > What > > we want is that a customer also sees the proper desriptions there. It is > > not > > only for different languages we want this, but also for different vertical > > markets where for instance a table should be called 'Campaign' one time, > > and > > 'Project' another time. > > > > Is there a querybuilder and reportbuilder that would support this (and can > > use EDB), or are there other solutions or ways to get this going the way > > we > > want to? > > > > Regards, Harry > > > > > > |
Fri, May 25 2007 5:36 PM | Permanent Link |
"Kim Madsen" | Hi,
Yes. Its in 2.70. -- best regards Kim Madsen kbm@components4developers.com www.components4developers.com www.myc4d.com - Your access to cool code The best components for the best developers Application server enabling technology for developers "Harry de Boer" <harry@staaf.nl> skrev i en meddelelse news:4222F987-6E2E-475B-B9A8-A23C457E145F@news.elevatesoft.com... > Kim, > > That's an interesting thought. Thanks! > > PS: any progress on EDB support for the 2.7 kbmMW release (will it be in > there) for June? > > Regards, Harry > |
Tue, May 29 2007 1:46 PM | Permanent Link |
"Herbert Sitz" | "Harry de Boer" <harry@staaf.nl> wrote in message
news:554ACED0-5172-4D85-AFB6-E91D337A44D2@news.elevatesoft.com... > LS > > My boss asked me an interesting question: can we make one of our apps in a > way that the tablenames and fields get descriptions that we want. We can > already do that (using TsiLang) with UI controls, but when we deliver a > end-user report mechanism where a customer could query the database himself > then the table- and fieldnames are the one as we named (designed) them. What > we want is that a customer also sees the proper desriptions there. It is not > only for different languages we want this, but also for different vertical > markets where for instance a table should be called 'Campaign' one time, and > 'Project' another time. > > Is there a querybuilder and reportbuilder that would support this (and can > use EDB), or are there other solutions or ways to get this going the way we > want to? > > Regards, Harry > I use Korzh EasyQuery query building tool that's quite good and easily lets you specify names different from fieldnames. Has a lot of flexibility, you can even hide table structure from users to make things simpler. http://www.korzh.com EasyQuery just provides a simple UI for users to define queries and EasyQuery then spits out the SQL. I combine EasyQuery with the DevExpress QuantumGrid and ExpressPrintingSystem for a really great end user reporting solution. Dead simple for users, and QG provides a lot of flexibility for them to tailor results how they want before printing. The setup I described isn't perfect for all reporting needs, but in many cases this combo can be much better solution for end-users than a "real" report designer like ReportBuilder or Crystal Reports. It depends on what you want. -- Herb Sitz |
Wed, May 30 2007 5:02 AM | Permanent Link |
"Harry de Boer" | Herbert,
Thanks. I will look into the Korzh product. We use Fastreport however instead of EPS because we need to print invoices, contracts etc, that are not possible in QG/EPS. Do you know if Easyquery can be combined / work with EDB and Fastreport? Regards, Harry "Herbert Sitz" <hsitz@nwlink.com> schreef in bericht news:5B114595-89C6-47D7-BD96-BC1D2B7976C5@news.elevatesoft.com... > "Harry de Boer" <harry@staaf.nl> wrote in message > news:554ACED0-5172-4D85-AFB6-E91D337A44D2@news.elevatesoft.com... > > LS > > > > My boss asked me an interesting question: can we make one of our apps in a > > way that the tablenames and fields get descriptions that we want. We can > > already do that (using TsiLang) with UI controls, but when we deliver a > > end-user report mechanism where a customer could query the database > himself > > then the table- and fieldnames are the one as we named (designed) them. > What > > we want is that a customer also sees the proper desriptions there. It is > not > > only for different languages we want this, but also for different vertical > > markets where for instance a table should be called 'Campaign' one time, > and > > 'Project' another time. > > > > Is there a querybuilder and reportbuilder that would support this (and can > > use EDB), or are there other solutions or ways to get this going the way > we > > want to? > > > > Regards, Harry > > > > I use Korzh EasyQuery query building tool that's quite good and easily lets > you specify names different from fieldnames. Has a lot of flexibility, you > can even hide table structure from users to make things simpler. > http://www.korzh.com > > EasyQuery just provides a simple UI for users to define queries and > EasyQuery then spits out the SQL. I combine EasyQuery with the DevExpress > QuantumGrid and ExpressPrintingSystem for a really great end user reporting > solution. Dead simple for users, and QG provides a lot of flexibility for > them to tailor results how they want before printing. > > The setup I described isn't perfect for all reporting needs, but in many > cases this combo can be much better solution for end-users than a "real" > report designer like ReportBuilder or Crystal Reports. It depends on what > you want. > > -- Herb Sitz > > |
Wed, May 30 2007 12:14 PM | Permanent Link |
"Herbert Sitz" | "Harry de Boer" <harry@staaf.nl> wrote in message
news:7B09FA49-5ADF-4EDD-909B-DF015619D97F@news.elevatesoft.com... > Herbert, > > Thanks. I will look into the Korzh product. We use Fastreport however > instead of EPS because we need to print invoices, contracts etc, that are > not possible in QG/EPS. > > Do you know if Easyquery can be combined / work with EDB and Fastreport? > > Regards, Harry > Sure, like I said EasyQuery is just a UI component that lets user specify a query. Once user has specified the query you have them click and a button, then behind the scenes you access the SQL from EasyQuery that corresponds to the query the user specified. Then you can just feed the sql into a query component, execute, and use any report writer to do reports against the data in that dataset. Unless you alter them, though, the fields in the sql and thus the dataset would have the field names from the database, not the names that the user saw in EasyQuery when specifying the SQL. I solve this problem by using a table as a sort of "data dictionary" that holds fieldnames and corresponding display name. I hold this in memtable on the client and just loop through to set displaynames the first time a query is opened on the client. I think this may be necessary only because I work with disconnected datasets in kbmMW. Don't most BDE-replacement db's allow you to define a display name for a field that is then passed to the datasets and used for display instead of the actual field name? FastReport sells its own query building tool, too: http://fast-report.com/en/products/visual-query-builder.html -- Herb |
This web page was last updated on Friday, April 19, 2024 at 07:09 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |