baanprog
13th June 2005, 10:16
Hi,
I want to capture values entered on form for the CRDD session.
What kinds of solutions are available?
Regards
norwim
13th June 2005, 14:39
Hi there,
since it is a tools session I can't think of any practical way.
What you could try though is to use the DEBUG switch when starting the bshell. Make sure that only one user can access the tools menus and that this user always has DEBUG activated. Easy to do with ba6.1, tricky with GUI.
But this has some drawbacks, first of all that you will have to rename the files with the debug-information to keep them, but secondly (and this is the main problem) these files may get REAL big.
May I ask why you want to capture the input?
regards
Norbert
baanprog
13th June 2005, 19:09
Iam trying to capture whether the proper values were put in or not as a check.
Its a like post mortem.....
Regards
lbencic
13th June 2005, 19:55
There are things with wrappers and / or api's that you can do to track this.
API: You could make your own session that looks just like CRDD, same inputs (ok, similar, because you can't use tt domains). You can put logging to a table or file of your choice, then use api's to call the stadnard CRDD session, assuming API's work. I have not tried this.
Wrappers (QKEY, RMCgen, rush): You can wrap the CRDD session itself and put your logging before the continue process. The wrappers will have the tools issues too, but we have gotten around this before with table entries...if that's the option you are choosing and have problems post up, I will try and answer.
baanprog
14th June 2005, 06:31
Hi Lisa,
That was wonderful.... I was thinking only API calls as the solution and the reason i made the post is to know whether any other solution existed...
Can you please give me more info regarding Wrappers, I will appreciate that.
Regards