No, access rights to write to a file are the issue, not old school or new school.
The issue is that when you write to a file, nobody else should be able to interfere.
That means just the opposite of what you wrote: During writes, not reads, the data should be locked.
Although complex merges of data being eddited between multiple users are possible to some extend by buffering.
Which is what most SQL flavors do.
@derek.jhon.evans
Thanks for your replys. You used one word, "neither", to ask my question, and then 2 posts to submit sugerences that implicates change the way how the existing application manage the data. Im sure your methods are better, but i still have no clue why neither of the proposed ways is good and why.
PS Methods proposed are simple ways to guarantee that any issue openning the file will be catched, and the file will be close at finish, without crash the app.
@derek.jhon.evans
You used one word, "neither", to ask my question, and then 2 posts to submit sugerences that implicates change the way how the existing application manage the data. Im sure your methods are better, but i still have no clue why neither of the proposed ways is good and why.
Also note, Pascal file commands arnt guaranteed to raise exceptions, so IOResult should be checked. But, I think Ive said enough :-)