March 8, 2012 at 6:57 pm #31301
I’ve upgraded to the latest version of COv4 and an exciting thing has started happening.
The following statement in the ‘Report Source’ for a report used to work prior to the application of the latest version:
LTRIM ( RTRIM ( per.firstname ) + ‘ ‘ + RTRIM ( per.lastname ) ) AS _payername
Now it crashes.
I’ve removed the LTRIM and associated parantheses and it works fine.
I appreciate that it’s not the end of the world (although I have to search through all the reports to find this type of statement) but have you any insight you could offer?
The build is 1068, the database is 1.067 and it’s .NET 4 Full Version.
Adminboy.March 9, 2012 at 12:08 pm #33003SupportKeymaster
Thanks for your post. To be honest I’m not sure about the LTRIM and RTRIM SQL commands. Please try substituting that enter line for the following :-
@NAME:per as _payername
The ‘@NAME’ function is a ClinicOffice extension which calculates the full name based on the name format in your program settings.
Please let us know if this works for you.March 11, 2012 at 11:14 am #33004
Thanks for your reply.
I used to use the @name extension but I stopped using it (I think it was because where the records had no first name, @name produced a string that started with a space and thus messed up the sorts, therefore I use the LTRIM to remove the leading spaces from the concatenated string).
It was the same reason I stopped using @address.
I’m guessing it is down to my ignorance in how you’ve set up the extensions. Could you let me know how they work?
I’m sure you already have your own reference so just for information I use: http://www.elevatesoft.com/manual?action=contents&id=edb2sql
Adminboy.March 13, 2012 at 3:28 pm #33005SupportKeymaster
It’s not quite as simple as just looking up the EDB reference guide I’m afraid. ClinicOffice uses an intermediate SQL language as it has to be compatible with both EDB SQL and PGSQL, so certain functions may not be supported.
There shouldn’t be any leading or trailing spaces using @NAME, but you could try the following :-
TRIM(@NAME:per) as _payernameMarch 16, 2012 at 1:50 pm #33006
I’ll try that. Thanks.
- You must be logged in to reply to this topic.