accent over a

[Turansky]

Hello,

I have a form that people enter basic information. If someone enters their name and it has a special character in it like an accent over a

[Keith M. Davie]

Kent, the problem must be with the token and the way it is generated in the url. I just entered two names at my site using an accented e and n and had no problem (FMPro 4.0.v3) creating a new record. However, I do not carry the name as a token. Using 4.0 I am limited to the use of one token [and no inlineaction] and must be very selective. Perhaps you should use a unique identifier of some sort and call the name through an inlineaction.

[Turansky]

You are right. I changed names and tried a few different things and seem to only have the problem with this -Token name. I'm useing the tokens to search the database before creating a new record. How would I use a unique identifier with the input field. I guess I don't follow what you are trying to direct me to. Could you elaborate a little more please.

Thank you

Kent

[Keith M. Davie]

"I'm useing the tokens to search the database before creating a new record."

Ah, that is a problem since the unique Identifier (uid) likely would not be available until a record was created. However there is something which I don't understand. Why are you searching the db with a username before the creation of a record?

One of the things which must be allowed for is the ability for the database file to distinguish between Paul Simon the senator, Paul Simon the singer and Paul Simon the economist. Otherwise Paul Simon cannot use his own name. When Paul Simon the economist tries to create a record in your solution will it be allowed if a previous record exists for Paul Simon the singer?

I untie this knot with a ScriptMaker script checking two pieces of data in a db which is not connected through WC.

Perhaps one of the developers who disdains scripts will tell you how to handle your problem with tokens.

[Turansky]

I search the database with the token to see if there are any duplicate names that match. If not it creates the record and continues on with the process. If there is a match like Paul Simon it will display the match along with his city, state, and zip and asks if this is the Paul Simon or if there are multiple Paul Simons it will ask if one of these is him or not. The whole process works pretty good right now except for this naming of the token. I will have to rethink the way I do this maybe. I will keep researching this one. Thanks for the input.

Kent

[Keith M. Davie]

"...asks if this is the Paul Simon or if there are multiple Paul Simons it will ask if one of these is him or not."

Which assumes the client will be honest. There seems a need for a check and balance such as a unique password.