Hi Guys,

We have a sign up layout that you have to fill out (11 fields) for you to become a user. What we want to have happen is once the customer is finished entering data into the fields and clicks the Enter button two things will happen.

A script will check to make sure fields are not empty and error trap some of the fields where it’s reasonable to do so like.

Phone Number: (US only): 10 Numbers

Social Security: Number: 9 Numbers

Email address contain: (@ and .) etc.

If all criteria match they go to the next page. If the criteria is not met a message comes up saying, “You either forgot to make an entry or the information was not entered correctly. Please try again”. (Id like this message to be in a field and not a dialog box, as I understand dialog boxes do not work on the Web). Then the offending field/s would either be shown in a different color or have a Red mark next to the field/s.

If you would happen to have a sample file showing how this works I would really like to see it. If not your explanation would be most appreciated. I have FMP 9A.

Thank you,

Milo

I could make you a sample file, but it would be pretty obvious how to accomplish it by studying this:

http://www.databasepros.com/FMPro?-DB=resources.fp5&-lay=cgi&-format=list.html&-FIND=+&resource_id=DBPros000799

And think of the posibilities provided in:

http://www.filemaker.com/help/FunctionsRef-389.html

--sd

Hi Soren,

Thanks for your post. The two link examples were very helpful and I thank you for them.

I’m unsure how to write the script however. It has to,

• Check for any empty fields and proper entry

• Error trap specific fields

• Provide a message that the criteria is NOT met and Set up a note to come up, I would guess from a calc field (because dialog box’s don’t work on the web) saying “everything wasn’t entered correctly try again”.

• Make the error fields change color

• Then if everything is correct go to the next layout.

I’ve tried to write a script to do this but have had no success. How would you do that?

Milo

I suggest some kind of mixture between scripting and autoenter, say if you need to track down a missing field could it be done by Count(field1;field2;field3...etc) with the knowledge of how many it is when all it filled with propper values. But similar could custom functions play a role here:

http://www.briandunning.com/cf/360

http://www.briandunning.com/cf/41

It's not easy to make exact advice here ...it largely depend on the data or rather how wrongly it could be attempted entered!

--sd

Hi Soren,

I understand what you’re saying and I thank you for the other two links. There is one last thing you can help me with and that is how to set up the script for the two fields that requires a confirmation. I have

Email address

Confirm email address

Password

Confirm password

This is just to double check they entered the information correctly.

Then I still have the issue of another field that will tell the person the information they entered is not the same. The field would be empty as long as both fields matched. If they don't the field would read “The two entries are not the same”. Once both entries match the field would again be blank.

What do you think Soren?

Milo

Case( Email address <> Confirm email address ; “The two entries are not the same” )

Hi Fitch,

I set up a new calc field called EmailCheckCalc with the following calculation.

Case( EmailAddress <> EmailAddressConfirm ; "The two entries are not the same" )

The problem is I get the message "The two entries are not the same" as soon as I tab out of the EmailAddress field. How can the calculation be changed so the message only shows after you tab out of the EmailAddressConfirm field if it does not match the EmailAddress field? Also, how would you set it up so the user cannot move on until the two fields match?

I just thought of something else while I was doing the above. How would you check the email address to make sure it's unique from the other addresses in our file?

Thanks Fitch,

Milo

Edited September 18, 200718 yr by Guest

I hessitated relplying here, because I honestly not believe Filemakers IWP is up to that kind of security ... all traffic can be sniffed, by someone with less than altruistic tendencies. You need to change the solution into a CWP'ish instead!

Fitch is right in his reply, but... perhaps Steven Blackwell wish to expand here?

--sd

Hi Soren,

I just found out that we will not be doing IWP we are going PHP. I don't know if that makes a difference or not, but thought you should know.

Milo

Well - Relational structure and the design of CF's was my area of the IWP solutions we provided, all the bells and whistles and workarounds to make a web conveyed solution, emulate an application near touch and feel, was ny partners share of it.

When I wached Lance Hallbergs session at devcon '05, did I feel that we might have used endless hour's of time ...slightly wasted, since the PHP seemed so much more obivous a choise!

What I really liked about what I saw was the "inclusion" of code snippets, to make a special feature work.

Personally, do I not feel an urge to poke deeper into php, I do never ever sell turnkey solution, always the relations and algorithms only...

--sd

Try this:

Case(

IsEmpty( Confirm email address ) ; "" ;

Email address <> Confirm email address ; “The two entries are not the same” )