Bush

How do you track/differentiate something as simple as an address/phone # change, then?

Simple and I greatly appreciate your sharing that... but. Does it _really_ satisfy HIPAA? I mean, yes, we can answer the "who looked at my data?" question, but our data security/audit trail policy requires that I be able to record the FROM WHAT > TO WHAT data (HIPAA's big on data restoration). Ray's [nightwing] 2-field solution satisfies this requirement but an enormous kludge in that EVERY field to be tracked needs to be entered into the calculation. I need a nice combination of these two solutions... ooh, the struggles of a Filemaker nearnovice..

Interesting. I'm running 7.2 on a Win2k laptop. The font-fuzziness is gone. I'm delighted. And I don't have any speed problems, either. Now, not all my scripts are functioning correctly (why do I have to go WINDOW > SHOW WINDOW > oh there it is... to have the new layout appear?), but the physical elements seem to be ok.

Excellent suggestion, Ray. ToaR! However, how would you document that so that anyone coming after would know what the heck was going on/notice the doubled fields?

Not so, the file's not there. I emailed JMO about this and his response was: "I have only published this file on my book Scriptology." Which is interesting 'cause I don't own this book (although it's supposed to be a spectacular resource) and I _know_ I got MODLOG off his site. So. JMO did offer to email it to me, but I already have it; in fact, I'd written him asking if he minded if I forwarded the file to any who asked for it. That he did not address, so I'm gonna assume it's a NO. So. I guess I hafta refer you to SCRIPTOLOGY.

In our experience, you should try and avoid having actions performed on closing w/o disabling the upper-right-corner-X. We had a client whose program was not issuing the correct reports because we'd configured several actions to occur on exit, but these were not triggered by the X, which is how the client was quitting the App (DESPITE TELLING US SHE WAS GOING TO FILE > EXIT... ARRRG USERS!). SO. I echo Ray, here: check out the plugins available, or set up your data entry to perform the checks you want on field-exit/data-submission.

How interesting. I cannot find MODLOG on the site, either. It's a 3-cupper named MODLOG that's called Modification Log in the window. I have a copy of it, still, if you'd like I can zip it and email it.

I've yet to download your sample, but I just created a log using the MODLOG file (John Mark Osborne's site) as the basis for my work. I've run into the FIELD NOT FOUND problem, though, in the CASE (name <> name OLD, name OLD & " -> " name, address <> address OLD, address OLD & " -> " address, etc) calculation for actually writing the field-changes to the log. I got, however, far further along than a mere 11 fields before I hit this problem (probably more like 100 fields in). Does this sample of yours get around this by creating a new record for each change, so it's not writing to a log field associated with each record? How do I get around the limitation in my CASE?