Double-Clicking Disaster

CyberSport · September 17, 2001

I have a related double-clicking problem, but mine is not generating multiple new records. I have an error and an access log and can trace the problem as follows:

when a user clicks multiple times in the same instant (e.g., three clicks in one second), it causes the "database not open" message to appear.

Filemaker continues to run behind the scenes, but with no more web access.

It takes the computer being restarted in order to clear the problem.

Looking at the error log, it records that an "HTTP session has been connected" in the same second that the multiple click happens.

Now, I guess I could put that javascript code in every page to prevent the post from being re-sent. But why would the double-clicking be sufficient to freeze the database?

Thanks.

Anatoli · September 17, 2001

From another topic:

I do not understand what is this about fully. Maybe on Mac IE has problems, which are not in PC version.

OK, but I can see the problem, or the implication and Keith put that very nicely.

I am usually submitting forms via JavaScript. I fired up FM, have IE form in window on local machine and I did manage to click 3 times before the IE shows second screen.

No validation was done on FM side, not Required fields.

FM created only 1 single record and not 3.

The code I am using on submit button is:

javascript:document.newform.submit()

The form name is "newform"

You need to specify -new or -edit in hidden input tag

Will that help?

Keith M. Davie · September 17, 2001

Using the link provided by Jeff, I was able to edit for just the single-click (no field verification). I did not need to name the form action for the JavaScript. Instead I just used an instruction in the head:

<!-- Begin

var submitcount=0;

if (submitcount == 0)

{

submitcount++;

return true;

}

else

{

alert("This form has already been submitted. Thanks!");

return false;

}

// End -->

</script>

</head>

CyberSport · September 21, 2001

would you mind looking at my code? i installed the js like you wrote, but i'm still allowed to double-click. thanks.

cybersport

<HTML>

<HEAD>

<TITLE>Add student to roster--Step 1</TITLE>

<X-CLARIS-WINDOW TOP=83 BOTTOM=706 LEFT=77 RIGHT=989>

<X-CLARIS-TAGVIEW MODE=minimal>

<!doctype html public "-//w3c//dtd html 4.0 transitional//en"><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><SCRIPT LANGUAGE="JavaScript">

<!-- Begin

var submitcount=0;

if (submitcount == 0)

{

submitcount++;

return true;

}

else

{

alert("This form has already been submitted. Thanks!");

return false;

}

// End -->

</script>

</HEAD>

<P><FONT SIZE="+1">From this page, search for a current Cornell

student. You will be able to view his/her profile and then choose to

make the student active on a roster for a varsity team.</FONT><BR>

<BR>

</P>

<P></P>

<BR>

</P>

<CENTER><FONT SIZE="+1">Search for a specific student

athlete.</FONT>

<TR>

</TD>

<TD>

</TD>

</TR>

<TR>

<P ALIGN=right>First Name:</P>

</TD>

<TD>

</TD>

</TR>

</TABLE>

</P>

<P><BR>

</P>

<P>

</FORM></P>

</BODY>

</HTML>

Keith M. Davie · September 21, 2001

I just checked my pages again and am having no trouble with the double click using that code. I am creating but one record. And it looks like you are using the same code.

You are doing a -find and I am using a -new action tag. However, that should make no difference with the anti-double-click. The button should register only one request.

About your form action for the -find. Your client enters a last name and a first name. I take it that there are no two students with the same first and last names.

Why are you performing a sort? If you are finding but one record (student), what are you sorting? If you are finding two students with the same first and last names, what are you sorting? What is the purpose of the -lop tag?

What happens if only one field has data entered when the -find is requested?

Because you are going to need the two fields to be filled, you may want to check the original link provided by Jeff for this JavaScript. It includes code to make sure both fields are filled as well as the anti-double-click code. The JavaScript is fairly easy to adapt to your form for the field check.

Have you researched this forum or the cdml forum and found the link and references to the documentation on "exact search"? This is very useful to understand. It ultimately leads to broader abilities with the -find tag.

Keith M. Davie · September 22, 2001

Since you are performing a -find, how is the JavaScript not working to prevent a double-click? What happens with a double-click on your find? What are the db results, the browser results? And if you apply the same questions to a single-click?

CyberSport · September 22, 2001

Keith,

I have the option set up for one or both fields and for last name op=bw because my users don't always have the exact info for the student on whom they are searching. That being said, I don't want to insist on the user searching for both first and last name. If they do a search for a partial last name, I want them to have the names sorted by last name.

I'm still confused as to why the js won't work, though.

Thanks for your help.

CyberSport

CyberSport · September 24, 2001

Keith,

I'm getting the -find to work, whether or not it's a single or double click. The problem is that on some pages of the site, when users double-click, it prevents FMP from being accessed via web unless all is shut down and restarted. To prevent this from happening while I'm putting in the javascript and testing things out, I'm first testing on a "safe" page, one that does not lead to the "double clicking disaster."

Now, if some of these problems are not with the "submit" button but with the extended URL link off the front page, is there comparable javascript to prevent this kind of double-clicking?

Thanks

Krishan · October 3, 2001

I'm using the following code to prevent multiple records being created:

code:

<!-- Begin

var submitcount=0;

function checkSubmit() {

if (submitcount == 0)

{

submitcount++;

return true;

}

else

{

return false;

}

// End -->

</SCRIPT>

Then on your form button, put this:

The only problem with this Javascript is that, if I have not filled in a required field but clicked on the submit button.... then I will be prompted to fill in the missing fields but won't be able to send my form because I already pressed the submit button once before.

Can anybody please help solve this problem! Thanks. smile.gif" border="0

Keith M. Davie · October 3, 2001

Krishan, I am using the same code successfully, but I do not have the line you are using:

The original code (see thread in cdml forum) which Jeff referenced included the code for the empty fields with which you are having problems. Go to the cdml forum and find that thread (nervous finger or some such). The code from Jeff's link is easily adaptable. I have utilized the entire format as well as an abbreviated format for a single click. I am having no problems with any of this.

CyberSport, "Now, if some of these problems are not with the "submit" button but with the extended URL link off the front page, is there comparable javascript to prevent this kind of double-clicking?"

I'm sorry, but I can't provide an answer to the JavaScript side. I know that the url address from your action tag must be correct. Sometimes using a intermediary (blank-format file) Meta "Refresh" command can prove very useful in assuring a proper link/action.

cinolas · June 18, 2003

I have been experiencing the "database not open" problem for a long time now without knowing exactly what caused it.

I have successfully proven that the double-clicking disaster is the cause of my "database not open problem".

That's great ! thanks to all of you ! Now that I know what is causing the problem I can start working on a solution...

But before I get to this point I have a couple questions:

Why is this still a problem ? This problem occurs with both form submits and URL style tags. This means that if you ever double-click on ANY filemaker link AT ALL it can screw everything and give you the "database not open" message! which seems like A BIG PROBLEM to me! I have seen report of the "database not open" problem coming from FMP 4.0 users all the way to FMP 6.0Unlimited... shouldn't they have solved this by now? It seems that if my main product was a "web capable database system", solving this double-clicking nightmare would be my #1 priority!

Is it possible, since FMP is single threaded, that simultaneous or near-simultaneous clicks coming FROM DIFFERENT USERS would cause the same problem? My DB gets the "database not open" problem about once a day ! I can't believe that we seriously have one nervous-clicker per day !

It's a major pain to have to protect EVERY FMP LINK OR FORM SUBMIT with JS or a blank refresh page! Since my DB is not "mission critical" (and since I am lazy and not looking forward to protect every FMP link in my solution), I was thinking of setting up some kind of a monitoring gadget that would simply restart FMP whenever the "database is not open"... Anyone can suggest a monitoring system that would do just that ?

Just now I will try to contact FMP tech support to see what they have to say about that, hopefully I will find a way to speak with someone without having to pay $399 per incident...

I will post my conclusions on this thread.

Once again thanks to everyone.

cinolas · June 18, 2003

well apparently my "complimentary support" access code has expired....

Vaughan · June 19, 2003

I have a solution that's been continuously up for well over 12 months, and have NEVER had this problem.

Originally in FMP4.0v3 on an NT4 box, last month I moved it to FMS 5.5 (on Win2000 I think) and FMU 6.0v4 on a 400 MHz G4 running Mac OS X 10.1.5. Users are running a mix of Mac and Win, Netscape and IE. FMU is very stable on X IMHO. FSM might give troubles on X, but FMU appears solid.

Is it a setup problem at your end? Are the FMU and WC versions up to date? Web Security or Access privileges? Is IWP enabled? Are scripts enabled?

There is no way that your users could be dumber than mine.

cinolas · June 19, 2003

lol...

I'm thinking maybe this is not a problem with the Mac version of FMU... Anyone outhere having this problem with FMP Unlimited for Mac os 9 or X ?

I am running FMP 5.0v3 with WebCompanion v6 on XP Pro, we are using access privileges and custom web publishing. The solution does not use scripts but I don't know if the scripts are enabled or not (where do I find this setting ?)

Vaughan, are you able to make your DB crash by triple clicking on the FMP links ?

Any kind of solution that does not involve adding Java Script and blank refresh pages everywhere is greatly appreciated! Also any monitoring solution would be greatly appreciated!

Thanks again

cinolas · June 19, 2003

Can anyone WHO IS NOT HAVING THIS PROBLEM on a windows server help us figure out why they are not having this problem, thus why we are having this problem ?

Vaughan · June 20, 2003

I just double-clicked, triple-clicked and even quadruple-clicked on FMP links (not submit buttons) using both Safari and IE on Mac OS X, and nothing crashed or broke.

Are you running FMU as a service?

Anatoli · June 20, 2003

RE: I am running FMP 5.0v3 with WebCompanion v6 on XP Pro

Maybe that is the problem. We are still with NT4 and about now the W2000 servers looks like next step in 4-8 months.

I wouldn't touch XP with 10 meters pole.

cinolas · June 20, 2003

I can't believe how quiet this thread is ! This seems to be a MAJOR problem and it seems to affect any web solution served by FMP Pro or FMP Unlimited from version 3 to 6 inclusively.

So maybe YOU should check your online solution to see if your affected or not. That you are affected or not, if you are serving a web solution with FMP pro or Unlimited with no third party soft on a windoz box, WE WOULD REALLY LIKE TO HEAR FROM YOU ! Tell us about your setup, give us the URL of your solution etc...

I investigated on the extent of this problem and I can literally crash FMP powered sites on demand with 3 clicks!

I hope I wont have to go around crashing solutions for the sake of creating interest in this problem ;-)

So I am looking for people willing to help narrowing down the cause of this issue or a good suggestion of a monitoring system that would restart a FMP Unlimited when a DB stops responding.

I want to avoid the JavaScript/Refresh Page solution as it is a pain to implement and is not elegant. I'd rather find the cause if possible.

I would love to transfer the whole thing to a Mac but go convince my PC-Boss...

Thanks

cinolas · June 20, 2003

Vaughan : No I am not using FMU as a service... Maybe the platform/browser that does the clicks has something to do with it, besides you are now on a Mac which might just do the trick. What if you triple-clicked from a PC with IE ? Can you crash it clicking on submit buttons ?

Anatoli: Actually we were on Win2K Server just a couple of weeks ago and it was doing the very same thing (maybe a bit less frequently but not a big difference).

Forgive my previous post, I had not noticed the second page and thought that the thread had gone quiet...

Can anyone think of a monitoring system that would restart FMP when the DB stops responding ? It would not be a problem on a Mac (again) with AppleScript...

Thanks for the replies...

Anatoli · June 20, 2003

Cinolas, how about for start some replies to our questions and remarks?

cinolas · June 21, 2003

Anatoli : Forgive my previous post, I had not noticed the second page and thought that the thread had gone quiet...

I have just confirmed that I am not able to crash my solution from a Mac OS 10.2.6 with the latest IE or the latest Safari.

The problem seems to be caused by IE on Windoz.

Anatoli · June 21, 2003

We are running on NT4 server, IIS, WSC and FMU5 without problem.

I guess FMU 5 wasn't certified for W2k server. In another installation we did run FMU5 on W2k client OS also without problems.

Are you sure you have the latest versions?

cinolas · June 25, 2003

I have FileMaker Unlimited 5.0v3 with the webcompanion v6

I just checked on the FileMaker web site and they seem to be the latest updaters available.

Vaughan: I have confirmed that the problem doesn't occur when the triple-clicks are made from a Mac running OS 10.2.6 and the latest versions of Safari and IE. Can you crash your solution from a PC ?

cinolas · June 26, 2003

It's getting worse ! Now I get the database not open about 5 times a day !!

HELP !

cinolas · June 26, 2003

UPDATE

I finally spoke with a FileMaker tech support representative today, I explained the problem and the guy knew right away what I was talking about. He said the behavior is (hold on to your hats) NORMAL.

NORMAL !!! !! !!! !!!

That's a nice way of not taking responsibility for a major problem you've given up on!

So next time your late on your mortgage payment because you've received too many bills at once, just say "it's normal" and it will all go away...

Normal...pffttt....

Alright, I'm almost done venting...

The guy explained that whenever WebCompanion receives near-simultaneous hits, since it's single threaded, instead of putting them in line, it crashes (like any good software should, just ask Micro$oft). And this is normal, apparently THAT's why they designed the Web Connector. The hits may come from a double-click on a link or submit button or simply from near-simultaneous hits from different clients.

This NORMAL MAJOR FLAW has NOT been solved in 5.5 or 6 and they are NOT planning on doing anything about it. They made the webconnector, they "recommend" that you use it and that should be good enough...

The Web Connector should be installed on the web server... if your lucky like me, your web site is hosted somewhere else by some hosting service and only the database part is in your control. My hosting company has no intention of installing the Web Connector so FileMaker "recommends" that I find myself another hosting service... I guess if I want to find one that would install web connector, I will have to go to one of the really expensive FMP Hosting service... that or host at least part of the site myself... isn't that convenient ? It's such a usefull NORMAL feature that I am surprised they don't use it as a sale point on their web site...

Feel free to contact FileMaker to congratulate them on their most usefull NORMAL feature.

Montee de lait...

Anatoli · June 27, 2003

RE: The guy explained that whenever WebCompanion receives near-simultaneous hits, since it's single threaded, instead of putting them in line, it crashes (like any good software should, just ask Micro$oft). And this is normal, apparently THAT's why they designed the Web Connector. The hits may come from a double-click on a link or submit button or simply from near-simultaneous hits from different clients.

THAT IS ABSOLUTE RUBBISH!

When 2 computers are running in JS loop and firing something like 10 requests per second to our server, and FMU can handle that, that bloke doesn't know where the north is and FMI should fire him in next second.

RE: it crashes (like any good software should, just ask Micro$oft).

Grown up. All my MS software didn't crashed in 5 years more, than my last two Mac computers -- Mac 4400 and iMac in day!

kandon · June 27, 2003

I am experiencing this problem, but without any clicking. The databases that are opened on my server are not being seen by Web Companion.

Any other suggestions?

OSX 10.2.6

FM 6.0.4

cinolas · July 4, 2003

RE: Grown up. All my MS software didn't crashed in 5 years more, than my last two Mac computers -- Mac 4400 and iMac in day!

With all due respect, my opinions on Micro$oft software's level of quality has nothing to do with my age, regardless of your computer experiences.

---

If what you are saying is true (about the 10 request a sec not crashing your setup) then obviously the FM tech guy was wrong. But it is the closest I have to an explanation and potential solution to my problem.

Is your solution hosted by FM Mac or PC ?

I take it you are not using the web server connector ?

Can you describe your setup in details ?

Are you connecting FMU to DBs on a FM Server ?

Can I have the URL so I can show you how I can crash it ? (if you know your solution is solid...)

At this point, before I try to find a hosting service that will install the web connector, I am looking for alternate solutions or modifications to my current setup that would solve the problem.

Thanks for the help

cinolas · July 4, 2003

Well well well.... Anatoli you were right when you said that the FM tech was full of it... there was a simple solution to my problem...

(bow my head in shame)

I modified the access privileges for the web user (no password) to allow export of the records (as recommended by other users with the same problem) and BOOM can't crash the solution no matter how fast I triple click on my links.

ye !

I have only been able to test the solution myself so far, let's wait a couple of days to see if the error comes back...

Anatoli · July 4, 2003

That is great!

Where is the champagne?

MaxcyD · July 8, 2003

Is that what all those fireworks I saw on the Fourth of July was about?

All I can say is, this Thread has been one of the most helpful in solving a real pain of a problem I have had for at least 3 years.

My hat is off to all of you and thanks so much!

Maxcy Dickson

cinolas · July 9, 2003

It's been 4 days now since I allowed record export for the web user and I have not seen a single instance of the "Database not open" problem.

Anatoli · July 9, 2003

That is GREAT!

Pearce · July 10, 2003

Here are my 2 cents...

Running Mac OS 9.1 and FMU 5.0 v3 with WC v6 using CDML. I have a form that, when submitted, creates a new record. The form has a javascript to check to see if data exists in the required fields. There are no required fields set in the db. No password is necessary to access the entire file. I have a hidden input field in the form that has the same value as the submit button (-New). Using IE 5.5 on a Windows ME machine I click on the submit button as fast as I can (about 6 times) and then get the format page. I go to check the db and only one record is created. I check the error log and poof! there is the entry: HTTP Session Disconnected. Alas! I have found what causes those pesky HTTP Session Disconnected entries!!! Even better, the db is still alive and well to the outside world as new records are still created after my HTTP Session Disconnected entry.

I hope this helps someone.

Unable · July 10, 2003

Pearce, I believe what you are describing is a function fo the Browser Cache settings.

But I've been wrong on many occassions.

Sign In

Double-Clicking Disaster

Recommended Posts

Create an account or sign in to comment

Create an account

Sign in

Similar Content

Important Information