1/24/2011 10:45 AM | |
Posts: 12 Rating: (0) |
Anybody can help me ? |
1/24/2011 12:10 PM | |
Posts: 799 Rating: (42) |
hi violinette, I don't know any possibility (script function etc) where this would be possible. best regards |
1/24/2011 3:39 PM | |
Posts: 12 Rating: (0) |
... Do you have any idea to block my navigation button while my view isnot entirely loaded ? Thanks, |
1/24/2011 4:07 PM | |
Posts: 12 Rating: (0) |
Thanks for your answer but I don't want timer or sleep... Does anybody else know ? Anybody did not have the case ? |
1/26/2011 5:47 PM | |
Posts: 12 Rating: (0) |
Thank You ! I'm going to install it. |
1/27/2011 4:57 PM | |
Posts: 799 Rating: (42)
|
Thank you!!! This is what I wanted to know Access_Violation in pdlrtseh.logis a crash of the process "pdlrt.exe". This is the graphics runtime. So normally when error occurs you are unable to operate everything on the system. Mostly a crash of the pdlrt is caused by wrong vbs scripts (vbs scripts in process pictures (pdl) are handled by this process) There are two possibilities now: 1st: You will make some diagnostics with ApDiag or the global script diagnostic window and you'll find out where script errors occur etc. If you've find out you can fix this scripts and everything should work fine Second: You install the Microsoft userdump tool on your system (Download)(How to use)You prepare it for an automatic dump of the pdlrt.exe process (Access_Violation). Then you have to operate as long as the crash occurs and a userdump will be created. If you have the Dumpfile you have to contact the technical support team. The guys there can analyse the dump file and can find out, where exactly the crash occurs. BUT: They can only find out, where the crash occured this time. If there are more wrong scripts, it is possible that there is a next crash a few days later caused by another one. At the moment, I don't see any other possibility!!! best regards |
Follow us on