Custom Code problem

I have this very basic custom code in my report:
Public Shared Function Basis(byVal Value as Integer) As Double
Basis = Basis + value
End Function
When I call this code, using =Code.Basis(Fields!BWT.Value), I expect it to
be like a running total. But all I get back is whatever the value of
Fields!BWT.Value is, without it adding up. I know that I could use the
runningvalue function, but I am wondering why this code doesn't work?quite possible the value of the function is not static. So everytime you come
into the function the value is reset. Try setting a temp invisible textbox to
basis' value evertime it updates.
"dachrist" wrote:
> I have this very basic custom code in my report:
> Public Shared Function Basis(byVal Value as Integer) As Double
> Basis = Basis + value
> End Function
> When I call this code, using =Code.Basis(Fields!BWT.Value), I expect it to
> be like a running total. But all I get back is whatever the value of
> Fields!BWT.Value is, without it adding up. I know that I could use the
> runningvalue function, but I am wondering why this code doesn't work?

custom assembly permissions woes

i have a custom assembly that was working fine, and i've set the basic
permissions needed in the RSReportServer.config file and all was good
however i've just added functionality that uses
System.DirectoryServices and the new code works fine within
visualstudio but i'm quite confused on what i need to do to get it
working on reporting services.
i'll willing to give full permissions to the assembly - at least in
the beginning just to get it running.
KarlKarl,
The exception that gets thrown should describe the failing element (the name
of the secure resource thats broken the security rule)
Hint: take a look at the top of the RSServerPolicy.config file and you'll
see the security permission types - these should provide a clue to which one
you need to use
You'll need to assert this required permission too in your CA and you'll
also need to ensure your CodeGroup (where the CA DLL has been defined) has
the required level defined also.
regards,
- peteZ
"Karl Prosser" <klumsy@.xtra.co.nz> wrote in message
news:7156880c.0410110045.33f32ff5@.posting.google.com...
>i have a custom assembly that was working fine, and i've set the basic
> permissions needed in the RSReportServer.config file and all was good
> however i've just added functionality that uses
> System.DirectoryServices and the new code works fine within
> visualstudio but i'm quite confused on what i need to do to get it
> working on reporting services.
> i'll willing to give full permissions to the assembly - at least in
> the beginning just to get it running.
> Karl|||Hi Karl,
Did you ever find a solution to this problem?
I have made a few similar postings with no luck.
Works fine for System.Data.SqlClient but not with System.DirectoryServices.
Cheers,
Flon
"Karl Prosser" wrote:
> i have a custom assembly that was working fine, and i've set the basic
> permissions needed in the RSReportServer.config file and all was good
> however i've just added functionality that uses
> System.DirectoryServices and the new code works fine within
> visualstudio but i'm quite confused on what i need to do to get it
> working on reporting services.
> i'll willing to give full permissions to the assembly - at least in
> the beginning just to get it running.
> Karl
>