> If you are using a nested fuseaction, you have to suppress
> layouts "above" the nested fuse's layout. You will need to
> put code in fbx_layouts to avoid this by checking
> $fusebox{"isNestedCall"}, or an easier way is to set
> $fusebox{"nestLayouts"} := false in the display circuit of
> the nested fuseaction.
>
> Regards,
Aparajita,
I haven't changed the nature of the fuseactions, so if I'm using nested
fuseactions now, I was using them in the earlier version that worked. Does
nested mean the fuseaction is sent to it's own circuit? The first time I
display the form, it's just a url, not a fuseaction; after the post, if
there are errors I send a fuseaction back to the same switch to display the
form again, which must be the nested fuseaction?
I realize I forgot to mention my configuration which is Active 4D v 3.0.1
b7, 4D 2003.8 server on Windows 2000 behind a Webstar 5.4.x web server.
I'm not getting anything in $fusebox{"isNestedCall"}, so I'm guessing that's
because I'm not using the most recent version?
Sincerely,
Mike Vogt
Millennium Data Services, Inc.
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
