Field Security Question

[NYPoke]

This is kind of a cross between Define Fields & Script Maker, but I'll try it here.

We have a couple fields, that we really need to remain unchanged after the first time they are set (Account Number, Start Date). We recently had some problems with a couple getting changed.

We have defined the field so that it cannot be modified. We tested it from the layouts, no problem.

The problem looks like a standard FileMaker feature: You can change field values from a Script, even though they are marked as Non(Un?) Modifiable in Define Fields.

Does FileMaker (v5/6) provide a way to completely lock down the fields, including preventing Script Maker from making changes?

[NYPoke]

This is kind of a cross between Define Fields & Script Maker, but I'll try it here.

We have a couple fields, that we really need to remain unchanged after the first time they are set (Account Number, Start Date). We recently had some problems with a couple getting changed.

We have defined the field so that it cannot be modified. We tested it from the layouts, no problem.

The problem looks like a standard FileMaker feature: You can change field values from a Script, even though they are marked as Non(Un?) Modifiable in Define Fields.

Does FileMaker (v5/6) provide a way to completely lock down the fields, including preventing Script Maker from making changes?

[NYPoke]

This is kind of a cross between Define Fields & Script Maker, but I'll try it here.

We have a couple fields, that we really need to remain unchanged after the first time they are set (Account Number, Start Date). We recently had some problems with a couple getting changed.

We have defined the field so that it cannot be modified. We tested it from the layouts, no problem.

The problem looks like a standard FileMaker feature: You can change field values from a Script, even though they are marked as Non(Un?) Modifiable in Define Fields.

Does FileMaker (v5/6) provide a way to completely lock down the fields, including preventing Script Maker from making changes?

[-Queue-]

ScriptMaker can change any field except a calculation field. Just make sure you don't have any references to Set Field or Paste, etc. into those fields in your scripts and you should not have any problems. Or test that those fields do not already contain values before ScriptMaker is allowed to change them.

If [isEmpty(fieldA)]

Set Field [fieldA, someResult]

End If

[-Queue-]

ScriptMaker can change any field except a calculation field. Just make sure you don't have any references to Set Field or Paste, etc. into those fields in your scripts and you should not have any problems. Or test that those fields do not already contain values before ScriptMaker is allowed to change them.

If [isEmpty(fieldA)]

Set Field [fieldA, someResult]

End If

[-Queue-]

ScriptMaker can change any field except a calculation field. Just make sure you don't have any references to Set Field or Paste, etc. into those fields in your scripts and you should not have any problems. Or test that those fields do not already contain values before ScriptMaker is allowed to change them.

If [isEmpty(fieldA)]

Set Field [fieldA, someResult]

End If

[NYPoke]

Thank You, yes we have done that. My problem is trying to lock it down a little better in the long run. We have hundreds of scripts & try to keep them in order. But as the work gets done, it is way too easy for somebody to miss this part, especially with several people working on the files.

This will keep me out of trouble for a while, but when dealing with auditors, I would like to secure it better.

I figured this was the best I could do, just wondering if I was missing something.

[NYPoke]

Thank You, yes we have done that. My problem is trying to lock it down a little better in the long run. We have hundreds of scripts & try to keep them in order. But as the work gets done, it is way too easy for somebody to miss this part, especially with several people working on the files.

This will keep me out of trouble for a while, but when dealing with auditors, I would like to secure it better.

I figured this was the best I could do, just wondering if I was missing something.

[NYPoke]

Thank You, yes we have done that. My problem is trying to lock it down a little better in the long run. We have hundreds of scripts & try to keep them in order. But as the work gets done, it is way too easy for somebody to miss this part, especially with several people working on the files.

This will keep me out of trouble for a while, but when dealing with auditors, I would like to secure it better.

I figured this was the best I could do, just wondering if I was missing something.

[Ted S]

A handy utility would be a "where used" report for fields and other objects. Maybe our friends at FM will include something like this in the next release.

[Ted S]

A handy utility would be a "where used" report for fields and other objects. Maybe our friends at FM will include something like this in the next release.

[Ted S]

A handy utility would be a "where used" report for fields and other objects. Maybe our friends at FM will include something like this in the next release.

[Ender]

A handy utility would be a "where used" report for fields and other objects. Maybe our friends at FM will include something like this in the next release.

It's been a while since I've tried it, but doesn't the Developer version have such a feature (in the DDR?) If not, there are some third party tools that are pretty good at this. I like MetadataMagic.

[Ender]

A handy utility would be a "where used" report for fields and other objects. Maybe our friends at FM will include something like this in the next release.

It's been a while since I've tried it, but doesn't the Developer version have such a feature (in the DDR?) If not, there are some third party tools that are pretty good at this. I like MetadataMagic.

[Ender]

A handy utility would be a "where used" report for fields and other objects. Maybe our friends at FM will include something like this in the next release.

It's been a while since I've tried it, but doesn't the Developer version have such a feature (in the DDR?) If not, there are some third party tools that are pretty good at this. I like MetadataMagic.