Replace Field Contents without a dialog error

[Derek Zimmer]

I created a script that is triggered upon exiting the field using the "Replace Field Contents" function. It works exactly as I need it to unless I select the "Perform Without Dialog" option. Then I get error 406. When I un-select "Perform Without Dialog" it works fine again. I have repeatedly tested this.

When I do NOT select "Perform Without Dialog" the dialog comes up and I have to select the "Replace" button manually using the mouse. Since I will ultimately intend to "Replace Field Contents" on 10 different columns in the same script I am trying to skip the dialog without having an error. Any ideas?

[bcooney]

Welcome to the Forums, Derek!

Well, a 406, as you've probably found out is "Replace/Reserialize criteria are invalid" error.

Perhaps a context issue?

Using Replace is a bit dangerous, as it affects all records in the found set. Can you describe what you're doing in more detail? Perhaps a looping script would be better...

[Derek Zimmer]

Each record has a set of 10 separate dates. Each date represents when to mail a letter. If I change any one of the 10 date fields the remaining fields update based on a formula. For example, if I change the 4th date then dates 5-10 change automatically. This is all within a single record. Additionally, I want all of the records in the found set to change, i.e. for records 4-10 of all the remaining records in the found set to change to match the record I manually changed. I have set-up a dialog that will ask if I want to change all records in the found set or just the record I changed.

So it is working exactly as I would like except for the fact that I can't get the Replace Field Contents to work using "Perform without Dialog" checked.

Of course, I would be willing to try any alternatives.

[bcooney]

Yikes! This doesn't sound like a good data model. Ten date fields in one record.

I see a separate table to record the mailings, and a calc field in the parent to determine the next mailing date, perhaps keyed off a preference lag time.

Please describe the business a bit more.

[Derek Zimmer]

This database is for my direct mail. I upload my list of names and addresses. Then I populate the dates for when each mailing will be mailed. I enter the first date and the remaining 9 populate based on my intervals. I upload lists almost daily.

Separately in the same database, I do a search for mailings to be mailed out "today." This search will search each of the 10 date fields for dates matching todays date in every record. I will then print the mail pieces (letters and postcards) for the resulting found set.

However, there are days that I don't do mailings like weekends or being out of town. In these cases I have to change the date in the found set of records to the date I actually mail. This causes the remaining dates to change according to my formula. For example:

I upload a list of 100 people including John Smith. He is due a letter from me on 1/1, 1/8, 1/15, 1/22, and so on. But, I don't mail his letter on 1/8. Instead I mail it on 1/9. The remaining dates must change to keep the same intervals. So, the remaining dates automatically change to 1/16, 1/23, etc. I have to do this for all the records that were due to be mailed on 1/8 (found set).

I use this same database for mail merging the letters and postcards.

I hope this is clear. I'm not sure. :qwery:

[bcooney]

I think I understand. It reminds me a bit of a system I worked on.

I wouldn't have empty date fields for each of the mailing dates, but rather calc the next mailing date in the Person record using the last date a mailing was sent, and which mailing is due (#1, #2, etc).

As a mailing is sent, an Activity record is created that logs the mailing type (1,2..9) and date sent. In preferences, I would define the intervals between mailings. (You can get fancy and have a "cushion" so that no two mailing are closer than 7 days).

[Derek Zimmer]

Sorry you lost me. Could you explain in more detail?

[bcooney]

Hmm, where did I lose you?

Basically, the parent record determines which mailing and what date it is due, by looking at the related Activity records. So, you do not create any future dates, you just determine the next date.

[comment]

Try the attached.

NextDueDate.fp7.zip

[TexasClodhopper]

Just in case someone runs across this post again about "406" errors, I had the same problem and received a solution from Phil in the Filemaker forum.

The problem was that I was not putting the focus in the field that I wanted the Replace to work on.

Phil had a better solution: http://forums.filema...sts/1cea62448f#