Subject Re: Error Code 239 IDAPI error From Michael <michael@abstractservices.com.au> Date Wed, 18 Oct 2023 17:11:14 -0400 Newsgroups dbase.getting-started Ken, Yes, all files have been recompiled under 2019. Local Share is always set to True How large can we make SHAREDMEMORYSIZE ? I currently have it at 4096. Funny thing though, I just let it run overnight through the DBASE 2019 environment/editor and it was still running. Could there be a problem running it as an executable? What can I look for? Anyadvice is helpful at the moment. Michael. Ken Mayer Wrote: > On 10/18/2023 2:28 AM, Michael wrote: > > Hi Guys, > > > > I have recently upgrade from dbase 11 to Dbase 2019. All of a sudden i am getting random problems. > > > > Problem 1. > > a search screen looking up items through my database thats been running perfectly for years all of a sudden randomly after a random number of uses simply drops the entire program out, no warnings, no errors. Mind you the code has been running fine for years. This is now happening in several modules. What could be causing this? Whats changed in 2019? > > Did you recompile everything under dBASE 2019? If it was compiled under > dBASE PLUS 11, and the runtime engine lets it run, this could be an issue. > > > Problem 2. > > I dont know if they are related but recently I am running 2 x .EXE one for opeerator usage and the other runs in the background to copy data to another file on the server  so it doesnt disrupt the users. However, again randomly I now get Insufficient Memmory to perform this operation and crashes at random points. It seems like its chewing resources and after a random number of reads/writes all of a sudden it seems to lose table data and the errors are triggered when I next try to read a table. The programs have been running like clock work for years and now seem to randomly run out of resources which is strange as both .exe's only used a total of 80-90MB of RAM. Is there a way I can find out what its chewing up and why all of a sudden I get these random crashes? > > Check your BDE settings under the BDE Administrator. Start the program > with dBASE closed (and all dBASE executables closed). In the window > click the "Configuration" tab. Click the "+" by "System", then do the > same for "INIT". Make sure "LOCAL SHARE" is set to TRUE. > > You may need to work with SHAREDMEMSIZE as well. I don't know what the > best setting for that is, however. > > If you are running out of resources, you need to check your code and > make sure it is closing and releasing objects from memory. If you keep > opening more objects and not releasing them, this can be a problem. > > > I am at a loss, can anyone shed some light on this please? One last note I upgraded to DBASE 2019 because I couldnt compile the program in dbase 11, it seemed I used the maximum number of elements available. > > This is an issue that may be a problem here as well. See above. > > 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 >