Home
>
WinDev Forum
>
Topic
WD21 , frequently this error coming.Any solution ?
Posted by Biju-2
|
Biju-2
WD21 , frequently this error coming.Any solution ? April 03, 2021 10:17AM |
Hello All,
" Error at line 21 of Click BTN_BTN ( TBAR_Header) process.
iPrintReport function called.
You have no rights to access the 'RPT_RVPV1' element.
Contact an administrator of the application."
mainly on "after printing reports" frequently this error is coming. Any solution ?
TIA
Biju
" Error at line 21 of Click BTN_BTN ( TBAR_Header) process.
iPrintReport function called.
You have no rights to access the 'RPT_RVPV1' element.
Contact an administrator of the application."
mainly on "after printing reports" frequently this error is coming. Any solution ?
TIA
Biju
|
Re: WD21 , frequently this error coming.Any solution ? April 03, 2021 12:44PM |
Admin Registered: 5 years ago Posts: 501 |
Hi, the error message tells it all! You have >no rights< to execute this part of the code.
Kind regards,
Guenter Predl
office@windev.at
Kind regards,
Guenter Predl
office@windev.at
|
Re: WD21 , frequently this error coming.Any solution ? April 06, 2021 12:36PM |
Registered: 5 years ago Posts: 192 |
I get this error sometimes on the first project window even when I log in as SUPERVISOR (which basicly means I cannot start the application in the first place). But it is not really a rights issue.
After a full recompile everything is fine again. It looks llike sometimes the internal list of objects has messed up.
Arie
After a full recompile everything is fine again. It looks llike sometimes the internal list of objects has messed up.
Arie
|
Re: WD21 , frequently this error coming.Any solution ? May 07, 2021 11:34AM |
Registered: 5 years ago Posts: 28 |
Hi,
I also had such a notification today during runtime of our software (WD25). It turned out (in our case) that a report was run via iPrintReport () with one parameter, while no parameter was defined in the report itself. Although this is a programming error, it was not noticed by WinDev because it was a dynamic call (report name is in a variable used in the call). So that's not surprising. But the message that is given at runtime is completely wrong. The problem is now clear and resolved.
Regards, Stefan
I also had such a notification today during runtime of our software (WD25). It turned out (in our case) that a report was run via iPrintReport () with one parameter, while no parameter was defined in the report itself. Although this is a programming error, it was not noticed by WinDev because it was a dynamic call (report name is in a variable used in the call). So that's not surprising. But the message that is given at runtime is completely wrong. The problem is now clear and resolved.
Regards, Stefan