Okay, so "forensics" is kind of a dramatic term -- but it correctly describes what I'm trying to do:

Is it possible to determine the dates on which certain changes occurred to a database? Not the data itself (which changes constantly), but when a field got added or when a layout was added or altered. Just wondering...

Thanks,

--Chris

Hi Chris,

What you are wanting to do is commonly called Audit Log, or Field Modification Tracking. Here are 3 files that show how to do this written in your version of FileMaker. And, best of all, they are FREE.

Field Modification Tracker By: Bob Cusick

Modification Times By: Alberto Diaz-Hermidas

Tracking Modifications By: Steve Wilmes

Available at:

http://www.fmfiles.com/tnt2.html

I use the one by Steve Wilmes.

HTH

Lee

By the way, while you are at fmfiles.com, take a look around, as it is an excellent resource for future needs.

I'm pretty sure that the samples above are all designed for tracking changes to your data, not db structure -- changes to field definitions, layouts, etc.

AFAIK there's no way to do that. About the best you can do is use a documenter tool such as Analyzer to take "snapshots" of your files from time to time.

Hi Tom,

Thanks for correcting me.

Man oh man did I miss read this question. Gave Chris the exact information he said he "Didn't" want.

Hi Chris,

Tom is correct, there isn't much out there to help you track this kind file changes.

Here is another area at fmfiles that may be of help to you, there are several Analysis Tools there, none that I know of give layout and field changes like you describe.

http://www.fmfiles.com/dev1.html

Lee

Hi, Chris! On occasion when I wanted to check something like that, I had to resort to looking at old backup copies of the db to see when we implemented something. We did quarterly backups on the db so it was only a ballpark date but it was good enough. I imagine a detailed changelog on a db would be too big too fast.

--ST

Thanks, everyone.

Steve T's approach is the only one I could think of, but there are so many fields as to make even this kind of difficult. (I suspect arbitrary additions are bringing down slower client machines, but I wanted proof.)

Since there are other potential "abuses" going on with regard to the actual data, the tools Lee listed are still helpful. He was just reading between the lines.

____________________________

The more I learn, the more I see how little I know.

What would you do with this information?

If I could have been reasonably sure that the changes being made were related to the slowdowns being experienced, I would have been able to recommend a policy against unnecessary changes.

Patient: "Doc, it hurts when I do this."

Doctor: "So don't do that."