11-25-2019, 03:33 AM
Luiz,
I do it a little differently. It's a little more overhead, but I have a function that launches forms using the target form name as a parameter.
If a form isn't supposed to launch, I can launch a substitute from the same procedure.
There is a little more overhead, but not enough to matter. You can request a new form from your procedure, do testing and create exception behavior in a consistent way, before a new form is even requested from IW.
Note that using the form name as the parameter is arbitrary. It could as easily be a number but using the name constant makes it more readable for me.
The details of how you do that might be different, but the idea of doing your testing/branching before IW even knows what form you want might simplify things for you.
Dan
I do it a little differently. It's a little more overhead, but I have a function that launches forms using the target form name as a parameter.
If a form isn't supposed to launch, I can launch a substitute from the same procedure.
There is a little more overhead, but not enough to matter. You can request a new form from your procedure, do testing and create exception behavior in a consistent way, before a new form is even requested from IW.
Note that using the form name as the parameter is arbitrary. It could as easily be a number but using the name constant makes it more readable for me.
The details of how you do that might be different, but the idea of doing your testing/branching before IW even knows what form you want might simplify things for you.
Dan