Hi,

Initially when I saw that locking feature is removed in 8.5, I was fine with it.

Until I came across an issue, where locking is very important.

One of the database in a multi-user environment had a report which runs statistical numbers for the day.

But, in the previous version like 7.x. User will lock the database and run this report to avoid users inputting data while running the report.
Which of course make statistical numbers incorrect, if users are entering data while running the report.

Could you please tell us how we can handle this in the latest version 8.5?

Hi Arul, 

Long time no see -- how are you?

Any report is a snapshot of data up to a given time (if I run it today, it does not include data from tomorrow), so could you include some cut-off time in your routines?

Hi Adrian,

Nice to hear from you. Been busy.

This is an existing applicaiton upgraded from 7.1 to 8.5. I have to dig into it. To see what is happening.
My guess is. If user forgets to enter today's data before 2pm. Then it should become data for tomorrow.
If not, files they export will only contain today's data. And user enters as today's data after 2pm will stay undetected.
They won't catch it on tomorrow's 2pm run. I have to look at the code someone else wrote, to see what's going to first.

Thank you.