Subject Re: Error Code 239 IDAPI error From Ken Mayer <dbase@nospam.goldenstag.net> Date Fri, 20 Oct 2023 07:09:06 -0700 Newsgroups dbase.getting-started On 10/20/2023 5:37 AM, MichaelItaliano wrote: > Akshat, I think your onto something, yes, I do run timers in the second app that checks if new records a re written and then writes them to a server somewhere. > > This small app runs in the background, the main app has a few timers in it to check tables, online order and schedueled reports. Its been very stable and runs days on end without issue but once i have the other app running , it runs and works fine for 2 or 3 sometimes four hours and then all tables simply drop out, I dont know what it is doing. each app runs perfectly well for days when I run them together it destroys its reliability. I just want to run a second process that doesnt effect the main operation similar to a windows second user, so that the main app can run faster and independantly, if you know another way of doing this, please advise. The most important thing is to release the timers completely when they aren't being used, maybe even every so often in your code they should be released (perhaps after performing some task, release the timer, then create a new one ...). Timers are big resource hogs ... Ken -- *Ken Mayer* Ken's dBASE Page: http://www.goldenstag.net/dbase The dUFLP: http://www.goldenstag.net/dbase/index.htm#duflp dBASE Books: http://www.goldenstag.net/dbase/Books/dBASEBooks.htm dBASE Tutorial: http://www.goldenstag.net/dbase/Tutorial/00_Preface.htm dBASE Web Tutorial: http://www.goldenstag.net/dbase/WebTutorial/00_Menu.htm dBASE DOS to Windows Tutorial: http://www.goldenstag.net/dbase/DtoWTutorial/00_Menu.htm