i am creating a time sheet db with a new user function for people to add them selves to the datebase. i am trying to make sure that the new user is not in the database, i am currently using a pattern count on a value list items function to make sure the new name is not in the list.

but i have found that if the user enters a part of an existing name it find it and wont allow the new user name, so when a user called Ed tries to enter his name and there is already a Ted present it returns a 1 and my script rejects the name (should of seen that coming really)

so my question is this is there any way of a making a pattern count that is absolute and will only return a one if it finds a word that matches rather than a part of a word

i have thought about looping through every record to compare each name individually, but that would take a life time once the database gets going, so i would like to avoid this method if poss

Here is a solution to your problem, which should not be at all difficult to implement.

Simply replace your current PatternCount formula with:

PatternCount("

try this:

This is a global with a field validation. I took a text field and added a validation to it. then I took the field and turned it into a global field. It will keep the validation. If you turn it back to a text field go to field option in define fields, you can look at the validation.

Elements:

1. Three fields

gusername: global text with validation.

gpassword: global text

username: text field.

2. Relationship Self join.

Validate name

I don't mean to be contentious, but I just did a quick test with simple validation of a global text field using Todd's technique, and it worked like a charm.

When I posted the last message, I attached a sample file. I do not know how you can get it on this forum..:??

Wow! I believe you. I guess you must be using FMP5 or 6. I tested this on 4.1, where it certainly didn

Ok! Now I really do stand corrected. I just took another look at this in FMP 4.1 and in 5 and it worked in both. I

"i am creating a time sheet db with a new user function for people to add them selves to the datebase. i am trying to make sure that the new user is not in the database, ..."

Perhaps I'm missing something.

To me this seems to assume that, whatever the time sheet purpose, there will never be the situation where Paul Simon, the Senator, is already registered and either Paul Simon, the song writer, or Paul Simon, the economist, subsequently attempts to register.

Put another way, I have met Keith Davie. He is not me, yet we had an employer in common.