
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
> Yes, it's true. FileMaker drops every 150th record. Developers just work > around it. Shhh. Don't tell anyone! > Sorry, you're theory is silly. Possibly you are entering info while in > Find mode, i.e., you're really not entering anything at all. Tom, I know the difference between Find Mode and Browse Mode, so it's not that. What led me to my (silly) theory was that I did a find of records only for one day, then when I sorted them all the information showed. When I Showed All Records and executed the script, some info was missing. Each teacher's absence generates a new record. Each teacher teaches three periods out of four, and each period is broken into two halves. On-call teachers each cover one half of a period. So, if J. Doe is absent, and teaches periods 1, 2 and 4, there are six teachers who receive notifications. When I sort according to my script, sometimes (and only sometimes) I'll see that the information for period 2 only isn't included. Period 1 and 4 summarized properly. > If that's not the case, post your script steps and we'll go from there. > In article In pseudo-script it goes like this: 1. Find all records. 2. Find records in specific week (e.g. 11/24/2003...11/28/2003) 3. Sort (restore, no dialog), sort order: Date, teacher away, per 1a, per 1b, per 2a, per 2b, per 3a, per 3b, per 4a, per 4b. 4. Enter Preview mode 5. Pause 6. Print (Show dialog box) What should happen is that the first sub-summary (Date) sorts the days of the week, the second one sorts the teacher away, the next 8 sort by period. Like I said, it usually works, but sometimes parts won't summarize (e.g. per 2a and per. 2b don't show up in the print preview). Thanks again for any insights. B
| <-- __Chronological__ --> | <-- __Thread__ --> |