Data Validation in Runtime

[T-Square]

Yesterday, I presented the newest version of my database in runtime form to the newest of my clients, and I encountered a slew of problems that I hadn't anticipated (which explains the five different posts I sent up today).

One of the persnickettiest of these had to do with how my nifty program handled failures by my new client to input required fields. My interface makes use of multiple windows with navigation buttons that trigger scripts go from one screen to the next. In the full FM7 version, if you click one of these buttons before having filled in a required field, FM pops up a message that the required field has not been filled in, and stops.

On the runtime, however, this message was completely missing, and the runtime just left the screen up. If my button was to go to a new window, that window would open up, and the first would not get hidden (as I want). If my button was to either close the active window, or go to another layout in the same window, it would just not do anything.

Before I freak out and start looking at how many scripts I have to write or modify, does anyone know whether there's some quick way to manage these? I'm foreseeing having to write a complex error-trapping routine into every script (or write a free-standing one that has to get added to every script)--but I'd love to be told that I'm wrong!

Thanks,

David

[T-Square]

Well, it's five months later, and I haven't seen any replies. Is the question too esoteric? Am I REALLY the only person out in Filemakerland who's having troubles with data validation in the runtime?

[Lee Smith]

So where have you been?

It is your responsibility, as the Poster, to ensure you receive an answer to your problem, not the members.

If you don't receive a response within the first day or two, then [color:"red"] you need to come back and rattle the Thread a little.

I can guarantee you, that given the number of posts that we read and respond to daily, no one else is going to do it for you. Personally, if I happen on to one that has been inactive for over 48 hours without a response, I may ask if them if they are still needing an answer, but one that is older, I figure the poster either received an answer from a another source (there are other lists), worked out the problem on their own (or are still trying to), found an answer by reading the Manual, etc., or just didn't care enough to push for an answer.

As for your question, I don't have Developer v7, so I can't answer your question. Lucky for you, there are plenty others that can.

Lee

[Vaughan]

So you've left your client sitting there for 5 months waiting for you to get back with a demo that works?

[T-Square]

Lee, Vaughan--

Yesterday, I responded in full-flame to your posts. I deleted that message last night because I saw how wrong-headed that response was. Lee, my second message was my attempt to "rattle the thread." I waited five months for precisely the reasons you mention; I understand that others on the list are busy, and that my needs might not be highest priority for others. Vaughan, the problem is persnicketty but not critical, and I have been able to advise my client how to avoid the problem using human validation. So, they've been able to use the system without a fix for this. But I would like to solidify the system to prevent the problem in the future.

The longterm solution I have been looking at is to build a generic error routine that shorts out any script and takes the user to an error layout in a new window. I put a message in the Scripting forum to see whether anyone has ideas on the best methods for trapping errors.

David