Jump to content

Keith M. Davie

Members
  • Content Count

    1,192
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Keith M. Davie

  • Rank
    member
  1. When I signed in today to make a contribution of knowledge and experience I discovered the request for money. Since I am now living on a meager social security check of less than $1k/mo I will no longer be able to give my knowledge and experience away for free. Well, that has been my experience with FMPro. I have spent more on it than I have made from it. So I will no longer be attending to the needs of others since I cannot afford it. I depart leaving this bit of advice for all present and future visitors: Test your solutions with rigor while simulating multi-user activity.
  2. Golly whiz, ST, you've emphasized only one word of a two word phrase I'd suggest determined and tenacious. Novice means self-taught in FMP, written fewer than 25 ScriptMaker scripts, no idea that an event failure could occur, no knowledge of the meaning of "single-thread", only single-user developments and no programming experience. I'm not very clever, having made a financial loss for myself by becoming involved with FMP. The bankruptcy would seem to indicate that my insight must also be lacking and my logic is questionable at best. For the benefit of mattlight, who is using Pro7, an event failure means ScriptMaker did not function. This happens most often because ScriptMaker is in the process of performing an event (single-threaded or capable of performing a singular action) when a subsequent event request is made. Being already in use and lacking any queueing capacity ScriptMaker acts as if the subsequent event request were never submitted. The upshot of a failed event is the data can get "lost" by not getting processed through the ScriptMaker event. And when that occurs through a web submission the client is misinformed and led to believe the transaction was successful and the owner of the db files is not informed that an event was requested but not performed. And of greatest concern to you, a failed ScriptMaker event could interfere with the wooing of women while engaging in urban hang-gliding.
  3. Hi Lee, when did you get promoted to the Grand PoohBah of the Subject Line? Was a formal announcement made? Well I guess I missed that, but congratulations. Thanks for the instructional on my ability to edit the subject line. I'll keep it in mind if I ever feel the need.
  4. Pro6. There are many web examples in the Sample Files forum in Pro5 which are convertible to Pro6 which you may or may not find useful. The exact field match, above, is just one of the many examples to be found there.
  5. ScriptMaker is, AFAIK, single threaded and handles only one event at a time. Further, ScriptMaker does not queue subsequent event requests. A busy site is likely to receive near simultaneous event requests. If you are going to use ScriptMaker for web publishing, or in a combination of web publishing and peer-to-peer, you would be well advised to rigorously test your solution under heavy usage, including especially requesting ScriptMaker events. The longer a ScriptMaker event takes to run, the greater the opportunity for subsequent event request failure. In versions earlier than 7 the languages for web publishing did not, in and of themselves, recognize event failures. A dedicated FileMaker novice could create a way to cause the recognition of an event failure in the earlier versions.
  6. Re: (not server version) If you are going to serve the db online you will need the Unlimited version for the web. If you are also serving the db as peer-to-peer you will need the server version. If you are running ScriptMaker events, you will be limited to one event request at a time (no near simultaneous requests) as ScriptMaker does not queue event requests and CDML, in an of itself, does not recognize event failures. No matter what you are doing, I recommend rigorous testing of all solutions through at least six browsers and while making various near-simultaneous requests. Under such conditions no problems should appear.
  7. Thank you Stephen for your response. I'm glad to hear you have not have any problems. I know that rigorous testing of ScriptMaker was what prompted my solution to deal with events not performing. And to prove my solution I wrote one of those lugubrious (non-looping) scripts to make sure that causing an event failure would occur during rigouous testing. While testing I often made six near-simultaneous event requests on the same and differing scripts (some short and some intentionally long - 10-15 milliseconds. Be sure to emphasize the "looping scripts are no-no part", because so many developers want to edit many records with the click of one button. That was solvable with CWP and JavaScript, but with IWP's dominance in 7 I'm afraid the developers have been restricted in solution capability. I'd suggest that you provide a caveat about ScriptMaker's single-threaded nature and its inablilty to queue near-simulataneous event requests made from the web and the erroneous information to the client and possible loss of data which can result and which are not the fault of your plug-in. You might also say that your plug-in does not resolve these issues. Do not consider this as legal advice. Please consult with your attorneys for your own protection. Good luck.
  8. Dear Dude, The last I knew FMPro's ScriptMaker was single-threaded and did not queue subsequent, near-simultaneous event requests. Do you know something I don't know? I know that when a ScriptMaker event uses a pause, if another request is made during that pause, a single-threaded ScriptMaker will allow the subsequent request to run without completing the first request. Now what will the consequences of that be to your web site?
  9. Hi Stephen. I noticed your ANN and read the link. I did not see any caveats so have some questions. While this plug-in allows "multiple" unsupported script steps, does your plug-in queue near simultaneous event requests so that all requested events are performed or has ScriptMaker solved that issue in 7? Since Pro developers love to run looping script events, which I believe are "unsupported", does your plug-in allow looping scripts and how does that affect performance? Thanks.
  10. Well I hope you are progressing. Mixing db's can be as useful as mixing metaphors. ScriptMaker has issues. You are probably needing a major redesign. Go all FMP or all oracle or all some other avenue.
  11. Can you? Yes. Now the real question is should you? ScriptMaker is a single-threaded engine. It handles one event at a time and does not queue requests made when an event is running. This causes problems in a web based environment should multiple near-simultaneous requests be made on any script. To further complicate things, CDML in and of itself does not recognize event failures and will misinform your clients. This can cause a loss of data unless you have someone physically watching your db files every minute of the day. As to script.presort or prefind; these are, at best, ineffective on the www. The good news about running a ScriptMaker event on the web is that any novice should be able to develop a work-around to make ScriptMaker an effective tool with many, but not all scripts. I know because I did that as a novice. The bad news is I am not selling that solution. I offered it but no one wanted it. And it won't work with you presort anyhow. But you can work out the solution yourself within 480 hours if you concentrate only on that solution. Or you can discover other ways to accomplish that which you desire through creative thinking and hard work based on your understanding of the CDML Reference db. Have fun.
  12. This past week I was in a Goodwill store finding things I can afford. There I found (but did not buy 'cause I already have it) a copy of FMPro 4.0 with serial number and instruction book for all of $2.99! Ok. So 4 does not have inlineactions and only one token. But with my abilities to make ScriptMaker reliable on the web those shortcomings have never bothered me. What matters is that Pro 4 does not require unlimited or server versions and it allows CWP. If I had to get a new copy of Pro I would not get 7 but would have gotten that copy of 4 for a true savings and client service. Keeping in mind the idea is to provide service to data via the web, not restricted by the number of clients, I just thought I'd mention this realistic solution considering the problems and expense folks seem to be having with later versions, especially 7.
  13. My two cents worth. First, Gary is right. Perform the find and then check the db file to see what was entered, if anything, upon which the find is to operate. However, before you ever get to the find action for the interview there is something else you can do. Your opening page, findinterviewer.htm, provides a list of interviewers. When an interviewer is selected that person's IntvrID should be carried to the results page (name not given, but lets call it interviewer.htm for this discussion). So before you even perform the find you would be advised to place (temporarily) [FMP-Field:IntvrID] on the top of "interviewer.htm" to make sure it is attached to that page. From the link from "interviewer.htm" to a selected interview, what I fail to understand is why you would have a format file Interview05.htm. You should need only one results page (interview.htm) which would display the results regardless of the interviewer or the interview contents (number, source, whatever). And if you must access a disparate database file, have you considered using an inlineaciton on the interview results page to do so? Just incidentally, the link which you provide in your original post will find only the interviewer, if anything.
  14. Tony, it is a good thing that you are finding other ways than the use of ScriptMaker. ScriptMaker is single-threaded and does not queue near-simultaneous event requests. CDML (in and of itself) does not recognize when ScriptMaker fails to perform an event which can result in erroneously informing the client (and data loss). While it is possible for a novice to FMP to develop a workaround to the problems so that ScriptMaker can run effectively over the www, your employer does not want to pay you to develop that workaround. Aside from ScriptMaker as a tool for effective security to completely remove "privileged" data from web accessed db files, there is really no need for the use of that engine. Structure your -finds with symbols such as exact field match and range and use tokens. Learn about the working of the -lop. Sometimes -finds can be enhanced with inlineactions either through a refresh page or directly on the results page. Find results can be enhanced with the use of the fmp-if on the results page. There's lots to play with when using -find.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.