Subject Re: Error Code 239 IDAPI error From MichaelItaliano <michael@abstractservices.com.au> Date Fri, 20 Oct 2023 08:48:26 -0400 Newsgroups dbase.getting-started Hi Mervyn, Very basic standard code, like USE &filenamestr in slect() set index to tag Modified set filter  to modified = "Y" go top set filter to use I believe some thing has changed in the versions, all of a sudden I am getting drop outs I never had before. Akshat may be onto something with timers Any other thoughts? Mervyn Bick Wrote: > On 2023/10/19 13:46, Michael Italiano wrote: > ....... > > The only thing I have noticed is that the 3 modules it happens in has some legacy dbase commands for the tables and not local sql commands. > > Although it can be done it is better not to use both XDML and OODML in a > program when accessing tables.   Unfortunately OODML often requires more > typing than XDML to achieve the same end but it only has to be done once. > > What XDML commands are you using? > > > > > So i take it some commands wont work in 2019? > > There should be no reason why a command that worked in dBASE 11 causes > problems in dBASE 2019.  On the other hand, major changes will have been > made to the "innards" to justify the "Optimized" label for dBASE 2019 > and this may have upset internal housekeeping routines. It is, however, > surprising that it has taken so many years to surface. :-( > > Something to look for is the creation of objects in a loop.  If you do > this you definitely need to make sure you destroy these objects once > they are no longer needed. > > Mervyn. > >