D
Dominik Loewenstein
Guest
I found out some solutions to fix the problem. At first the tool can be found under \src\protools\_prospy.w this is the path from a procedure editor. When i look into the file their is a check if the log file is correct: lGoodData = ((cInput BEGINS 'RUN' OR cInput BEGINS 'FUNC' OR cInput BEGINS 'PUBL' OR cInput BEGINS 'SUBS' OR cInput BEGINS 'UNSUBS' OR cInput BEGINS 'EXEC' OR cInput BEGINS 'MARK' OR cInput BEGINS 'TRIGGER' OR cInput BEGINS 'NEW' OR cInput BEGINS 'SUPER' OR cInput BEGINS 'INVOKE' OR cinput BEGINS 'DELETE' OR cinput BEGINS 'PERSTRIG') AND NUM-ENTRIES(cInput,'|') GE 7 ). the problem here is the cinput BEGINS 'PERSTRIG' check. In the created log files PERSISTENT TRIGGER is not writed in short form. So it is possible to read the log file with ProSpy+ when u search and replace PERSISTENT TRIGGER by PERSTRIG. I think the better way would be to edit the *.w file of ProSpy, but every change i did to the file want not take any effekt. Maybe its like an .r-file that already exists with the older code but i dont find it. Last thing i figured out thet the ProSpy+ out of the developer studio seems to be a newer version and the problem dont exists, but i cant start any procedure from developer studio, so it only helped me to open an old file.
Continue reading...
Continue reading...