calculation field FM 8

Hello,

I have three fields: FirstName, LastName and Email address.
A calculation field : User ID = firstname_lastname  (calculation
being : Trim(firstname)&Trim("_")&Trim(lastname) )

When a new record is entered, I need to check if there already is a
record with the same first name, lastname and email address. If the
record exists, I need to add a one at the end of username
(firstname_lastname1).

Please Help!!!!!

Thanks!

On Mar 19, 6:15 am, Deepti <dpulavar...@gmail.com> wrote:
> Hello,
>
> I have three fields: FirstName, LastName and Email address.
> A calculation field : User ID = firstname_lastname  (calculation
> being : Trim(firstname)&Trim("_")&Trim(lastname) )
>
> When a new record is entered, I need to check if there already is a
> record with the same first name, lastname and email address. If the
> record exists, I need to add a one at the end of username
> (firstname_lastname1).
>
> Please Help!!!!!
>
> Thanks!
> Deepti

What happens if someone changes their name or email address? Will

On Mar 19, 7:15 am, Deepti <dpulavar...@gmail.com> wrote:
> Hello,
>
> I have three fields: FirstName, LastName and Email address.
> A calculation field : User ID = firstname_lastname  (calculation
> being : Trim(firstname)&Trim("_")&Trim(lastname) )
>
> When a new record is entered, I need to check if there already is a
> record with the same first name, lastname and email address. If the
> record exists, I need to add a one at the end of username
> (firstname_lastname1).
>
> Please Help!!!!!
>
> Thanks!
> Deepti

You don't say that you're using the User ID field to link to other
records, so I'll just answer your question.  Make it a text field with
an Auto Enter Calculation.  Set the calculation to the calc you
already have.  Uncheck the box that says "Don't replace..." and
check

On 2008-03-19 17:49:58 -0700, Helpful Harry 
<helpful_harry@nom.de.plume.com> said:

> It would do, but there are ways to work around it. I use the full name
> as the link field in one of my systems, mainly because it's easier for
> the data entry people than working with obscure codes.  :o)

Harry, exposing any key(link) field to users is an Industrial Strength 
Developer Mistake. Using fields that are changeable and editable by 
users to base key fields on is another.

Users see names and use names. This is most certainly easier than 
numbers or codes.

However, the system itself should use unique and unchangeable key 
values which then function whether or not the user-editable values 
change.

I can't imagine a system in which all a person's orders become lost if 
they get married and change their name...and then get divorced and 
change it again. And yes, it has happened among my clientele. Some of 
my clients are on their third or fourth name since I started working 
with them. NONE of their linked data has been lost.

Nor does it require "workarounds."   It's good solid robust design,
and 
there are NO arguments for using exposed, user-editable data fields as 
key fields.
-- 
Lynn Allen
--
www.semiotics.com
Member Filemaker Business Alliance
Long Beach, CA

Deepti <dpulavarthi@gmail.com> wrote:

> I have three fields: FirstName, LastName and Email address.
> A calculation field : User ID = firstname_lastname  (calculation
> being : Trim(firstname)&Trim("_")&Trim(lastname) )
> 
> When a new record is entered, I need to check if there already is a
> record with the same first name, lastname and email address. If the
> record exists, I need to add a one at the end of username
> (firstname_lastname1).

Don't do that. You'll regret it sooner or later. Use serial numbers
(auto-enter, protected).

> Please Help!!!!!

You're welcome.
--