Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM SQL » View Thread |
Messages 1 to 8 of 8 total |
Using Case Operators in DBSIAM |
Fri, Jan 20 2006 6:53 PM | Permanent Link |
"Simone" | Hello, I need help using Case stmts in DBSIAM 4.22 build 3. I am =
getting "Invalid use of non-aggregated column expression in Select SQL" This is my sql statement and it gives me the above error. SELECT dt."Transaction Code", dt."Initials", case when (dt."Transaction Code" in (13,14) then SUM(dt."Quantity") when dt."Transaction Code" in (22,26,9) then Count(*) end AS sumItems, case when (dt."Transaction Code" in (13,14)) then SUM(dt."Int Data = 1") when dt."Transaction Code" in (22,26) then Sum(dt."Quantity") end as SumTckts FROM "Daily Transactions" DT GROUP BY dt."Transaction Code", dt."Initials" ORDER BY dt."Transaction Code" Does not like me to use the IN operator in the case statement. Can you help me? Semone |
Mon, Jan 23 2006 5:37 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Simone,
<< Hello, I need help using Case stmts in DBSIAM 4.22 build 3. I am getting "Invalid use of non-aggregated column expression in Select SQL" >> It's a bug - DBISAM should be making an exception for CASE WHEN expressions (in this case, the IN clause) as well as IF expressions that determine the branching, but it isn't. A fix will be available in about a week in a new build. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Jan 26 2006 10:22 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
I think I'm correct in saying the fix for this will be in V4.22b5, but I've lost track somewhere. Am I right? Roy Lambert |
Thu, Jan 26 2006 8:24 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< I think I'm correct in saying the fix for this will be in V4.22b5, but I've lost track somewhere. Am I right? >> Correct. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Jan 26 2006 9:34 PM | Permanent Link |
"Ralf Bertoldi" | > I think I'm correct in saying the fix for this will be in V4.22b5,
> but I've lost track somewhere. Am I right? ...wouldn't it be nice if the bug fix would be in 5.0.0.1 next week.. <bg> ralf |
Fri, Jan 27 2006 9:42 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Ralf,
<< ..wouldn't it be nice if the bug fix would be in 5.0.0.1 next week.. >> Yes, it would be. But alas, it will not. I will have some screen shots available within the next week of the ElevateDB Manager utility, however. -- Tim Young Elevate Software www.elevatesoft.com |
Tue, Jan 31 2006 7:58 PM | Permanent Link |
"Ralf Bertoldi" | Tim Young [Elevate Software] wrote:
> Yes, it would be. But alas, it will not. I will have some > screen shots available within the next week of the ElevateDB Manager > utility, however. will the screen shots be "production stable" or just "beta"..? ralf |
Wed, Feb 1 2006 8:05 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Ralf,
<< will the screen shots be "production stable" or just "beta"..? >> Neither, they're simply screen shots. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, May 4, 2024 at 12:54 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |