Not allowing returns in fields

[George Swisher]

This seems like a simple thing but I can not figure out how to limit users from entering returns in fields.

I have some applescripts written that do not work when there are returns in a field.

How can I either limit users from entering them or how can I create a script to remove them from a field when exporting?

[stanley]

George:

You could parse for carriage returns when passing your data to the AppleScript.

-Stanley

[Ted S]

Make your field validate by calculation:

PatternCount ( Field_Name; "

[BobWeaver]

The other option is to simply let the user enter them, and then delete them using a calculated field with the formula:

StoredField= Substitute(InputField,"

[George Swisher]

wow, a lot of options. Thanks for all the info. Probably would be best to remove them when exporting but I still want to keep the data seperate. Some users type in a notes field with returns to seperate each item. If I just remove the returns, the information will run together. Is there a better way to replace the returns with another character or does someone have a better suggestion?

This is a VCF card export function I built so there are a lot of fields and may be too time consuming to create a calculated field for each removing the return. I like the val calc that will not allow the user to enter a return but also want to protect the export to remove the return in case something is missed.

Stanley, How can I do this on the export in apple script? Keep in mind that I already have an appleScript to export a calc field formatted for a VCF card. I am guessing that I will just add this part before the export function.

thanks all!