On Jul 1, 2006, at 2:19 AM, Steven McPhelan wrote: The problem with the Parameter approach is that you have to essentially emulate what Fileman is doing. Everytime your code is called, you have to save the last entry that user entered and then store an appropriate value in your parameter. Of course, you have to recall the parameter value each time in order to get the default value. If you are using interactive Fileman calls what is the advantage of using parameters instead of Fileman's method? If you just want to remember the last lookup value, there's nothing to do: just let Fileman take care of it (and be sure you don't include "F" in DIC(0), of course!) But if you want to do something else, then you are NOT duplicating the work Fileman is doing. Beyond that ^DISV is a data structure meant for Fileman's internal use (just as ^XUTL is there for the internal use of Kernel). It is simply poor design for one application to start mucking around in the internal data structures of another (and it's all the worse when the other application is infrastructure). Gregory Woodhouse "Judge a man by his questions not his answers." --Voltaire |
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
