--- Kevin Toppenberg <[EMAIL PROTECTED]> wrote:
> Are you saying that you have tried, for example, putting a "^" in the > middle of a text entry for a field, and it is accepted?? This would > introduce terrible field-shifting errors that Chris mentioned! I've > not tried this myself, but if you have done it, I'd like to see a > screen log of the interaction. > > Kevin > No, this is for extract fields. If the storages is E1,250 then characcter positions 1 through 250 are used for storage. If only part of a node is used for an extract field and the rest is "^" delimited and that throws of Fileman, that's a bug. My rule of thumb is: 1. If it's MUMPS code, put it in a MUMPS field. 2. If it's not, but is of any reaxsonable length, put it in an extract field. 3. Otherwise, consider (un)encoding with $$HTML^DILF. Using an output transform, you can make this transparent to anyone but one of those nasty :-) programmers that insist on doing global reads. === Gregory Woodhouse <[EMAIL PROTECTED]> "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
