![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 31 to 35 of 35 total |
![]() |
Fri, Aug 12 2011 9:12 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | Michael
The offer still stands, if you can let me have enough to try it I'll see if I can figure out what's going on. Roy Lambert |
Fri, Aug 12 2011 10:25 AM | Permanent Link |
John Hay | > I don't know anything about FR, but you can use a simple test to prove what > I'm saying - just pop a query into the EDB Manager that references a valid > table with a correlation name, but then references an invalid column name > using the table correlation name, like this: > > SELECT * FROM customer c > WHERE c.customerno=1000 > > (customerno doesn't exist) > > Then check out the error message - EDB does not add double-quotes around the > column name in the error message, therefore the double-quotes are not being > added in the error message, and they're certainly not there in the original > query. Change this to the following and you do get double quotes. As the report previews fine after the error a wild guess would be that the error is a result of somehow inadvertantly running a faulty query. SELECT * FROM customer c WHERE s.customerno=1000 John |
Fri, Aug 12 2011 10:40 AM | Permanent Link |
Roy Lambert NLH Associates ![]() | John
>Change this to the following and you do get double quotes. As the report previews fine after the error a wild guess >would be that the error is a result of somehow inadvertantly running a faulty query. > >SELECT * FROM customer c >WHERE s.customerno=1000 Fascinating Moriarty. So if Michael did a cut'n'paste on the query in his original post we're looking for something that looks like an S but isn't an S. You've done a lot better than I have. I couldn't find a way to replicate the error. Now all you have to do is explain how the report still displays properly after the error ![]() Roy Lambert [Team Elevate] |
Fri, Aug 12 2011 10:51 AM | Permanent Link |
John Hay | Roy
> Fascinating Moriarty. ![]() > > Duff one first and good one second? That was my guess. John |
Mon, Aug 15 2011 4:14 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | John,
<< Change this to the following and you do get double quotes. As the report previews fine after the error a wild guess would be that the error is a result of somehow inadvertantly running a faulty query. >> Bingo, that's it. So, it's definitely a case where the wrong table correlation name is being used. -- Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 4 of 4 | |
Jump to Page: 1 2 3 4 |
This web page was last updated on Monday, July 15, 2024 at 07:03 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |