The docs say that data stored in the location can contain "^" but I'm not sure if FileMan will check if the field being entered is an extract storage type before it kicks out the "^" user input. After some experimenting it appears that if the data starts with "^" the input is ignored otherwise it is accepted.
Of course, if you're using a custom input routine you can get the data in there as internal format., you'll just have to have a special read for their input so it doesn't go through FileMan. If you cant get your users to not enter the ^, you could always store it in a word processing field. At 04:42 PM 7/5/2006, Greg wrote: >Using extract mode (as you describe) is probably the simplest solution. >Another option is to use $$HTML^DILF to encode special characters as >hex. The trick here is that you need to unencode the data in the output >transform and be sure to use $$GET1^DIQ instead of global reads to gedt >the data. If you want to be able to read input containing an up-arrow, >you can specify the "U" flag in ^DIR. (By the way, this is one time >when RECALL^DILFD can be quite useful). 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
