Best way to protect files from being inadvertently written over in filemaker

what is the bast way of protecting a file from being inadvertently written over
for example unless i make a new record i still have the old record on the screen and if someone forgets
to specify a new record they cna easily overwrite the old one
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

you can have 2 layouts, one which is read only,  and a 2nd one where you can access the fields, and use a button to switch to the 2nd one; at least you have to press a button before you can modify anything.
other way; 2 accounts per user; 1 which can edit records, the other not. when a user wants to modify a record, you relog him under another account with a button+script. quicker done than having to double the layouts.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
gevensenAuthor Commented:
i was thinking about a lock script that would dis allow entering the fields when a fake save button was pressed then to edit you have to press edit on any existing files to allow you into the fields again

does that sound feasable

ive been busy today writing reports and havent had a chance to play with the idea

lesouef, you would be surprised how far i got since i asked those few questions
no easily, the ony way I can think of is using the validation feature of each field to check that button state. too much work really, the account method is less work, though not clean since it prevents data changen but fields are still accessible, so the user a warning msg: making the field read only would be better, but fmaker does do that yet. obviously everybofy at filemaker ignores even javascript?!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
FileMaker Pro

From novice to tech pro — start learning today.