Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Enhancement Requests and Suggestions » View Thread |
Messages 1 to 8 of 8 total |
SQL Suggestion |
Tue, Aug 8 2006 6:16 AM | Permanent Link |
adam | Small enhancement suggestion which would no doubt be hell to code (!)
Ability to SELECT MasterTable + Concatenate a Field from Child Table into a memo or blob of the result. i.e. SELECT C.CustomerName, CONCATENATE(O.OrderNumber) FROM Customer C LEFT JOIN Orders O ON ... |
Tue, Aug 8 2006 6:33 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | adam
Anything wrong with just doing it like this... select _Forename, _Surname, _mainphone, _Notes+#13+_MainPhone, cast(_Mainphone as memo) from contacts left join career on _ID = career._fkcontacts where _id = 7 _Notes is an existing memo field in contacts, _MainPhone is a varchar(25) in career Roy Lambert |
Tue, Aug 8 2006 9:33 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Adam,
<< Small enhancement suggestion which would no doubt be hell to code (!) Ability to SELECT MasterTable + Concatenate a Field from Child Table into a memo or blob of the result. >> As an aggregate operation, correct ? IOW, keep appending to the same result row BLOB value for all of the child table values ? -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Aug 8 2006 10:03 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Ahhh. I totally misunderstood what was wanted.
Roy Lambert |
Fri, Aug 25 2006 9:14 AM | Permanent Link |
adam | Deqr Roy & Tim,
Sorry to be slack in writing my request ... What I wanted was the ability to create a "list of children" i.e. Table1: Customer Table: Orders Result: CustomerName, OrdersIDField -- OrdersField would be a blob or memo listing all Orders ID fields: The reason this would be useful for me is I have an TIDFieldList component, which takes a list of integers and displays them as "hot-links" (blue when you hover-over). Users like it because it shows a whole lot of orders (or other children) in very little space & they just have to click to navigate to the Order. The Order then has a similar TIDFieldList for OrderItems ... -- To make it work at the moment I have to iterate a child query & parse then child query IDs into a variable in Delphi ... which works well, but is a bit clunky. Adam |
Fri, Aug 25 2006 10:17 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | adam
I'd use a dbgrid and a master-detail relationship. The "goto order on click" functionality is a doddle. Roy Lambert |
Thu, Aug 31 2006 5:11 PM | Permanent Link |
adam | >>Roy Lambert <roy.lambert@skynet.co.uk> wrote:
>>adam >>I'd use a dbgrid and a master-detail relationship. The "goto order on click" functionality is a doddle. >>Roy Lambert That's true Roy, but often the user doesn't really want a big "2 grid master detail" type GUI for every single situation. With my solution the user "sees" a single record (i.e. customer X), which contains what looks like a memo field with a simple list, but they can click on the elements of the list to open a detailed rendition of the data for that element. Grids are good, but there are often times when other ways of displaying the data give a much more "sensitive" GUI for the user. Adam |
Fri, Sep 1 2006 3:41 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | adam
Turn off the indicator, titles, grid row lines and column lines and you have a very good resemblance to a memo field. I do that quite a lot to display some forms of tabular data. Roy Lambert |
This web page was last updated on Wednesday, April 24, 2024 at 11:07 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |