1 of 1 people found this helpful
as far as point 2, ensure the user that the Orion report is running has rights to run the SQL command (whatever - check permissions).
if you run it within report writer, I assume it hangs there too? any error messages?
I've never tried to create variables on the report side, maybe try making this a stored procedure and calling it from the report writer (should be able to send variable from report writer statement for customername, just have to have a report per customer still).
anyways, some thoughts/things to try.
for point 1, I would think there is a way, just how to access it...this would have to be SW or someone that plays with .net a lot.
I could also use this type of thing as I have a few customers that see their info....
thanks for the reply.
I guess you mean I have to check if the sql user I created for solarwinds has acces to build the report I created?
I've just made this user an admin on the sql server. when I then connect as this user to the sql server and I run the query it works like a charm. If I try it again in the report writer and it is the same problem. Is there perhaps a solarwinds service that I should check and run as a user?
As I was typing this message I just read about the stored procedure again. If I do it this way it seems to work fine so problem solved :)
now for the first part.. any .net players arround?