Subject Re: Error Code 239 IDAPI error From Akshat Kapoor <akshat.kapoor@kapoorsons.in> Date Sat, 21 Oct 2023 15:31:42 +0530 Newsgroups dbase.getting-started Good Afternoon MichaelItaliano, > 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. I know the source but do not have a solution. I can just suggest alternatives. Use Windows task scheduler to schedule tasks if the gap between the tasks is more than a few minutes. (I use this to take backups every 30 minutes) If the timer is scheduled to fire every few seconds (Where I discovered the issue) I will suggest initiating the task using windows scheduler every say 30 minutes. The app checks if a app by the same name is running or not. If a app is running then let it run and shut down the current copy otherwise you have a new copy up and running. I have not used this approach but can be achieved. If you are interested in this will post code which will help you in this. Regards Akshat