![]() > What experience have you had after making this change ? > Has anyone out there modified this (progress side) parameter on their > Have you installed the latest and greatest progress patch? > No, I worked with tech and progress to fix the locking problem. > Maybe I will get some good tips from that. like nullfixer.r and any other tools I should run and > I am going to post another question about how to do maintenance on the So every night, we clear stale sessions and reports that are > that had been running in the background for days, everything went back to > in our database! When we had a record lock timeout and cleared a report ![]() > putting a filter partnumber so it was running where used for ALL 80K parts > locked, a user had run a big report, mostly where used report WITHOUT We did find that every time our records were They had no idea why our records were being locked and just told us > obviously getting very frustrated and vantage support was, of course no > the record lock would clear and their record would save. But if we instructed them to wait 30 minutes, Once the user clicks save, the vantage screen just turns white and They could access all records but just couldn't save > process transactions but no one in vantage could save or add any records, During the record timeout, MES could still > We got this Record lock timeout error pretty frequently (twice a week) Why would they lock a record when the report is only reading the information Most of the reports donÂ’t just read data butĪctually compile data into tables first and then read it, and then clear the
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |