Subject Re: Error Code 239 IDAPI error From Akshat Kapoor <akshat.kapoor@kapoorsons.in> Date Mon, 23 Oct 2023 15:51:50 +0530 Newsgroups dbase.getting-started Good Evening Michael, > I have used this method in the past, but sometimes the windows scheduler is irractic and it doesnt server the purpose of running a quick live update. > > The reason I used a timer in a second .exe is to have a process running in low memory in the background to update a large combined transaction file on a server in a multiuser environment. I notice once we get to 300K+ records dbase BDE seems to get tired and lags, multiple that buy 5 terminals all trying to update live, the user experience drops to a crawl. Not very practical in a live environment. > > So I noticed that removing this step keeps it running efficiently and as windows only allocates a maximum 50% of processor to each dbase exe, I thought having a second process running in low memory in each terminal may keep the processing speed up on the user end. It was due to system slowdown that I have shifted to MAriaDB using ADO. With MariaDb the system doesnot slow down. The dbase exe which is run by windows task scheduler is a backup file. It creates a backup after every 30 minutes. For time interval of 15 seconds dbase Timer is the only option Regards Akshat