T
tbergman
Guest
It's possible I'm missing something here but I believe the OP is referring to difficulties when running programs from the AppBuilder/PDS. If not, then here's my problem. When testing a form using AppBuilder, either in PDS or separately, the .w gets run persistently by adecomm/_runprog.p. _runprog.p contains its own WAIT-FOR and it's a conventional GUI WAIT-FOR, not the .NET style. This makes it very difficult to test a .w from within the AppBuilder/PDS because if the .w then opens a .Net form, errors will occur. I could certainly customize _runprog.p but I shouldn't have to.
Continue reading...
Continue reading...