Re: Need to recompile reports 3.0

when connecting to a different database during runtime than the one you were connected during generation causes this error. As far as i found out this happens, if there ar program units doing a sql-statment on the database. we solved the problem as follows: we have defined a role with access-rights to the tables. this role is granted to the application user, but the user has this role not by default.
create role myapp_user identified by xyz; grant select any table to myapp_user ;
grant myapp_user to application_user;
alter user myapp_user default role none ; In the reports builder select in the object browser on top of the tree the report name and in the property palette enter this role (i currently do not now the property but i think it is the last entry in the property palette).
in this way the application user cannot acces the data outside the application (e.g. viw sql/plus) while he has a report open. From now on you must always enter the roles password ("xyz" in the obove example) when you open it in the report builder. by the way: be happy not to work with graphics...same problem, no workaround
pawan_at_ggn.hcltech.com schrieb:
>
> We have migrated our Applications from D2K ver1.1(16 bit) to D2k
> ver2.1. The rep files of all the reports are installed on client
> machines. We have to periodically recomile the reports i.e. regenerate
> the reps.
> The error code that is shown in the Reports Background engine is REP-
> 1439.
> In the help, the solution given was to either recompile the reports or
> use the rdf file instead of rep. We can not do the latter for security
> reasons. So please help me if you have any other solution for the above
> problem.
> Thanks a ton in advance..
> Kamlesh
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Wed May 17 2000 - 00:00:00 CEST