goesflavio
26th May 2006, 01:57
Thanks until now
Hi every bory,
I make a program that run a tisfc0102m000. My problem is when I have to backflush ths hours, because my real spent hours dont appears in the tisfc0102m000, but this occur when I run with a session that I customized, but when I run with a standard tisfc0102m000 this do not occur, the hours stay ok.
I already debugued the programs and see that when the program is run the tihra1210s000, when is executed by customized program, in the cont.process is executed command print.data that dont is executed correct. Exemple:
choice.cont.process:
on.choice:
execute( print.data )

choice.print.data:
before.choice:
||When I execute by standard tisfc0102m000 this function heve been executed correctly, but when I use my customizes program, this function do not be executing and go to after choice.
backflushing.my.hours()

after.choice:
do.something()

ps.: My baan version is c4 and SP8

Sorry for my English.
Best regards.

mr_suleyman
26th May 2006, 08:10
I am not sure about it . Did you check session's form default options ? Option 23 is enabled ?

Good luck !

goesflavio
26th May 2006, 15:49
Thank you advance, but dont worked. This problem is extranger, I think that is environment. I do the same function in the after choice if do not to enter in before.choice.
Best regards

mark_h
26th May 2006, 17:20
I am not sure I understand - which session did you modify tisfc0102m000 or tihra1210s000? Did you modify anything other than the scripts? Did you add the before.choice section on print.data? When you the session you modified manually does it execute this section? On fishing expedition to see if something clicks.

goesflavio
26th May 2006, 17:29
I did a program that invoque the tisfc0102m000, I did nothing in the tisfc0102m000, but when I try to call my program (customized), the tihra1210s000 dont work the before choice of print.data.

mark_h
26th May 2006, 20:00
Hmmm - so you added the before.choice to tihra1210s000? I ran a test on my system which had a before.choice and on.choice sections. All of the sections worked fine when calling with the stpapi commands. I am beginning to think you are correct that it is in the environment - one of the sessions or your stpapi libraries.

Of course you can always try using the api.mode variable in the on.choice section of print.data. Example:

choice.print.data:
on.choice:
if api.mode then
.....customized code here.......
endif

But I really do think it should work as is.

goesflavio
26th May 2006, 21:02
Hi Mark, its funny, because when check every variables of environment its ok. I wouldnt like to use this api.mode because there are very program that can use this program now or in the future.
Thants a lot Mark for your advise.
Best regards

mark_h
26th May 2006, 21:27
Actually what I was thinking was using this as a temporary work around. I have had to do this before while waiting for Baan to fix things. So as a temporary work around you might be able to do this:

choice.print.data:
before.choice:
if not api.mode then
....run your code.....
endif
on.choice:
if api.mode then
....run same code as above.....
endif

As bad as that looks it should always work - until you find a permanent solution. We have actually used something like that in work arounds - not in those session or sections, but in other parts of code.

goesflavio
26th May 2006, 21:34
Dear Mark, I already make your advise, thanks a lot for you spend your time with my problem.
Best regards.