Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 8 of 8 total |
DisplayName for SQL columns |
Tue, Mar 21 2006 11:30 AM | Permanent Link |
In a TDBISAM table, I can set the DisplayName for each field. Is there a
way to do this in the SQL query too, from the SQL itself? Sort of like: SELECT MyField1 DISPLAYNAME "User name", MyField2 DISPLAYNAME "Home address FROM MyTable I realise it may not suit everyone, but I can't use permanent fields as I don't know what fields I'll have except at run time. My code currently returns all the internal field names, but I'd have to work out all the display names separately and a shortcut would be nice. 8-) /Matthew Jones/ | |
Tue, Mar 21 2006 11:34 AM | Permanent Link |
"Robert" | "Matthew Jones" <matthew@matthewdelme-jones.delme.com> wrote in message news:memo.20060321162901.3692E@nothanks.nothanks.co.uk... > In a TDBISAM table, I can set the DisplayName for each field. Is there a > way to do this in the SQL query too, from the SQL itself? Sort of like: > SELECT MyField1 DISPLAYNAME "User name", MyField2 DISPLAYNAME "Home > address FROM MyTable > Almost got it. SELECT TABLEFIELD DISPLAYNAME.... You can not, however, set a mask. Robert |
Tue, Mar 21 2006 1:52 PM | Permanent Link |
Michael Baytalsky | Hi Guys,
You can do both with Context Extensions, but only for the fields declared in schema, so you can't do that for calculated fields for example. All you need to do is: 1. Use TDBISAMDatabaseExt & TDBISAMQueryExt 2. Have TDBISAMDatabaseExt connected to TDatabaseSchema 3. Have all tables, fields and their properties defined in Schema (Description is DisplayLabel, EditMask, DisplayFormat and DisplayWidth are awailable) 4. Turn AutoFieldProperties property True for TDBISAMQueryExt or use dbExtUtils.UpdateFieldsFromSchema(Query, Database) after you activate Query. It will take table/field names from Origin property (DBISAM is nice enough to actually fill it with correct info) and lookup information from Schema. This feature is only available for DBISAM extensions and won't work for BDE, because it doesn't always supply Origin property. Regards, Michael Robert wrote: > "Matthew Jones" <matthew@matthewdelme-jones.delme.com> wrote in message > news:memo.20060321162901.3692E@nothanks.nothanks.co.uk... >> In a TDBISAM table, I can set the DisplayName for each field. Is there a >> way to do this in the SQL query too, from the SQL itself? Sort of like: >> SELECT MyField1 DISPLAYNAME "User name", MyField2 DISPLAYNAME "Home >> address FROM MyTable >> > > Almost got it. SELECT TABLEFIELD DISPLAYNAME.... You can not, however, set a > mask. > > Robert > > |
Tue, Mar 21 2006 3:42 PM | Permanent Link |
Looks like I have some reading to do. This is part of the standard DBISAM
shipment yes, not an additional library? /Matthew Jones/ | |
Tue, Mar 21 2006 4:14 PM | Permanent Link |
Michael Baytalsky | > Looks like I have some reading to do. This is part of the standard DBISAM > shipment yes, not an additional library? I'm not sure I understand the question. It's certainly a part of standard shipment for Context Database Extensions for DBISAM (both 1.x & 2.x), but not of DBISAM by Elevate. This is why we call our package "extensions" You can get it here: http://www.contextsoft.com/products/ctxdbext Regards, Michael |
Wed, Mar 22 2006 4:59 AM | Permanent Link |
Thanks - this may sound odd but I don't think I ever heard of it before.
A note on the text of your scripting: (sorry for off topic!) "Component library designed to incorporate reach scripting functionality into Delphi application." should be "Component library designed to incorporate RICH scripting functionality into A Delphi application." /Matthew Jones/ | |
Wed, Mar 22 2006 8:14 AM | Permanent Link |
Michael Baytalsky | > Thanks - this may sound odd but I don't think I ever heard of it before. I should advertise more, I guess > A note on the text of your scripting: (sorry for off topic!) > "Component library designed to incorporate reach scripting functionality > into Delphi application." should be > "Component library designed to incorporate RICH scripting functionality > into A Delphi application." Thanks, I've corrected this. I'm not a native speaker, alas, so grammar is a bit of a challenge Regards, Michael |
Wed, Mar 22 2006 9:44 AM | Permanent Link |
> I'm not a native speaker, alas, so grammar
> is a bit of a challenge I guessed, hence me thinking it worth pointing out. /Matthew Jones/ |
This web page was last updated on Saturday, June 22, 2024 at 05:51 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |