Showing posts with label expression. Show all posts
Showing posts with label expression. Show all posts

Tuesday, March 20, 2012

No "Left" function in Expression Builder?

Anyone know the reaon the Left function was left out of the list of string functions in the Expression Builder?

Danno

DannoCoy wrote:

Anyone know the reaon the Left function was left out of the list of string functions in the Expression Builder?

Danno

No. Annoying isn't it?

Instead you can use REVERSE(RIGHT())

-Jamie

|||I think SUBSTRING would be slightly faster for simple operations. You got your nesting the wrong way round as well, but we know what you mean.|||

DarrenSQLIS wrote:

I think SUBSTRING would be slightly faster for simple operations. You got your nesting the wrong way round as well, but we know what you mean.

Oh you're so picky :)

Friday, March 9, 2012

next line

is there a way in an expression that I can tell it to carry over to the next
line?Yes use:
= Fields!MyField1.Value & vbCrLf & Fields!Fields2.Value
HTH,
Magendo_man
"Ben Watts" wrote:
> is there a way in an expression that I can tell it to carry over to the next
> line?
>
>|||Thanks very much
"magendo_man" <magendoman@.discussions.microsoft.com> wrote in message
news:3FEEEFCD-B686-4FD4-80EB-D9EDCFF5916D@.microsoft.com...
> Yes use:
> = Fields!MyField1.Value & vbCrLf & Fields!Fields2.Value
> HTH,
> Magendo_man
> "Ben Watts" wrote:
>> is there a way in an expression that I can tell it to carry over to the
>> next
>> line?
>>

Wednesday, March 7, 2012

NewLine and Carriage return issue in PDF format

If I insert the following expression in a textbox it will display
correctly in HTML format but not in PDF format. Can anyone show me how
to accomplish the same thing so that it will display correctly in both
HTML and and PDF format.
vbCrLf & vbCrLf & vbCrLf & "My Text"
In HTML format, it will display "My Text" on the 4th "row". Whereas in
PDF format, it displays "My Text" on the first row of the textbox.This has to be an issue (bug) with PDF and how it formats initial blank
space before the literal text. I am not sure if this is addressed in a
service pack for 2000 or in 2005 (I am using 2000 to test this) but here is
a workaround that I found that places an ASCII record seperator in the first
position before the CRLF's as:
=CHR(30)&vbCrLf & vbCrLf & vbCrLf & "My Text"
That should work.
Rodney Landrum
<Nergock@.gmail.com> wrote in message
news:1143588675.322590.215140@.u72g2000cwu.googlegroups.com...
> If I insert the following expression in a textbox it will display
> correctly in HTML format but not in PDF format. Can anyone show me how
> to accomplish the same thing so that it will display correctly in both
> HTML and and PDF format.
> vbCrLf & vbCrLf & vbCrLf & "My Text"
> In HTML format, it will display "My Text" on the 4th "row". Whereas in
> PDF format, it displays "My Text" on the first row of the textbox.
>

Saturday, February 25, 2012

newbie: value expression... uses an aggregate expression w/o a sco

simply added a report parameter for a working report (which went fine and w/o
issue..)
next thing, went to build the report in VS.NET and got 100 Build Errors
telling me that every TextBox on my summary page has the error:
'The value expression for the textbox '...' uses an aggregate expression
with a scope...'
Newbie (I know), but what on earth did I do that would have screwed up
everything like this?
( Scope for what? The report and parameters already have everything they
need as far as data goes.)
Rob(this is a frickin nightmare...)
So it looks like every time I try to add a new report parameter, after
deleting the original (simply the report parameter became a different report
item), about half of the textboxes which are sums and counts threw this error
(which is nutty as heck, since about 2/3, which have the same thing are OK).
Is this some kind of bug? (Deleted all Report Parameters and I can compile
w/o errors.)
What's going on with this and what does it take to 'set the scope'.
Rob
"RobKaratzas" wrote:
> simply added a report parameter for a working report (which went fine and w/o
> issue..)
> next thing, went to build the report in VS.NET and got 100 Build Errors
> telling me that every TextBox on my summary page has the error:
> 'The value expression for the textbox '...' uses an aggregate expression
> with a scope...'
> Newbie (I know), but what on earth did I do that would have screwed up
> everything like this?
> ( Scope for what? The report and parameters already have everything they
> need as far as data goes.)
> Rob
>