Subject |
Re: Error Code 239 IDAPI error |
From |
Mervyn Bick <invalid@invalid.invalid> |
Date |
Thu, 19 Oct 2023 15:42:45 +0200 |
Newsgroups |
dbase.getting-started |
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.
|
|