popup update question (was: Re: Nested Gosubs)

[Fairlight]

You'll never BELIEVE what GCC Consulting said here...:
> 
> Mark,
> 
> If you do a popup update to the current file, @w processing works.  It still
> doesn't work to a lookup file.

Ah, well there's a good feature to add, then.  @when processing on lookup
files.

> The best way to handle this is to create a duplicate screen using
> dummy fields and us @w processing on the dummy fields and the post the
> information to lookup

Way too much legwork.  BTDT, which is probably why I remembered it at all.
That's one of those areas were the R in RAD falls off until you're done and
can glue it back on.

I don't care how it's done, particularly, although I can think of a few
ways.  (One of these would be internally using @uef/@ulf, etc., and writing
a separate prc to handle a table.  Then you could specify a prc to use in
the actual (modified, of course) popup update command, so you could support
it for more than one PU per main table.  Just off the top of my head.

But it's one of those things that could be implemented and would be a VERY
nice addition to the current suite--it would make it consistant..  

mark->
-- 
Bring the web-enabling power of OneGate to -your- filePro applications today!

Try the live filePro-based, OneGate-enabled demo at the following URL:
               http://www2.onnik.com/~fairlite/flfssindex.html