Reports not running thru' DAS

Hi listers,
I am facing a very peculiar problem here. We have a lot of reports that we fax to our customers thru’ DAS residing on a NT server. The report uses a custom script and fetches Fax nos. from the OUTLOOK (Contacts) of NT Box.

We for a major development now changed the User Groups (in a nutshell split the original User group into two) at Supervisor level. The permissions for the ID which we use to schedule reports thru DAS has exact same permissions in new user groups as earlier.

We sent this report again after the changes but get “NO DATA TO FETCH”. But, we know we should have data (Verified thru a local run). What could be the things we could be missing out for the report not to work ? Any suggestions here are welcome.

I have a strong feeling that we are missing some thing that needs to be set explicitly after the same Id has been added into new groups, but don’t know what. Also, I could be wrong.

Thanks,
Vinay.


Listserv Archives (BOB member since 2002-06-25)

Can you log on to the DAS box and run the report THERE as your DAS user?

I wonder if there is a connectivity issue / difference that comes into play on that box, like a local TNSNAMES, ODBC connection, etc. that kind of stuff would get resolved on the DAS box at run time, maybe there is an issue there…

Custom connections are a good idea, and we use them here - that makes me lean towards the TNS ( I am going out on a limb and guessing oracle)

Good luck,
Brent

Hi listers,
I am facing a very peculiar problem here. We have a lot of reports that we fax to our customers thru’ DAS residing on
a NT server. The report uses a custom script and fetches Fax nos. from the
OUTLOOK (Contacts) of NT Box.

We for a major development now changed the User Groups (in a nutshell split
the original User group into two) at Supervisor level. The permissions for
the ID which we use to schedule reports thru DAS has exact same permissions
in new user groups as earlier.

We sent this report again after the changes but get “NO DATA TO FETCH”. But,
we know we should have data (Verified thru a local run). What could be the
things we could be missing out for the report not to work ? Any suggestions
here are welcome.


Listserv Archives (BOB member since 2002-06-25)

I have found that some perfectly valid report with perfectly valid queries are returning the message “no data to fetch”. After telling my users that they were crazy I started to see it for myself. Whenever 3 or more dimensions are used in a query I need to make sure that whatever objects are referenced in the “where” clause must also be in the “select” clause. For example if you want to see products sold to a particular customer, then the customer code needs to be in the “select” clause even though each row returned will be for that customer. Don’t know if this is you problem, but it is one thing to check out. Simon


Listserv Archives (BOB member since 2002-06-25)