Is there any way to force a script to take the default value for an ask.enum and continue on when the session is running in a job? The ask.enum produces an error and kills my process (or at least prevents it from running correctly). Surely there is a way around this...:eek:

BTW, at the moment, this is for Baan 4.

Ed,

You can code it in your script as -

if not (api.mode or job.process or background) then
if ask.enum("zmadm0002", zmyeno.yes) = zmyeno.yes then
start.process()
endif
endif


Hope it helps you out.

I guess I should have gone into more detail. What if there is no code available for the function in question or it is not allowed to be changed? For example, the ask.enum is in a library function or several function layers deep in a library call. What then? Is there anything that can help here?

There is no way to trick the system into this -
but if its standard Baan and "Make Job Process" is an option, then this should not happen and it is a bug.

Dave

Well, I am trying to run a session that has "Make Job" available. That's irritating...

The other route I attempted to pursue was using AFS and answering the question ahead of time. However, this system is a 4c3 system and that AFS function isn't supported in 4c3. One suggestion I heard was to update the ttstpapihand library and standard program to the 4c4 versions. What are the potential problems with this course of action???

I'm not that familar with AFS's, but it seems to me that if the
program doesn't have the job part down correctly, its probably buggy in the AFS handling area too...

Dave