AV in FR_Class.InitDataSet
Hello,
In FR_Class.InitDataSet, somewhere in: CreateDS(Desc, DataSet, IsVirtualDS),
I get an AV at 4CDE4F9F in 'IDPDX32.DLL' read of address 0.
When I retry opening the report after that error I also get error
'Index out of bounds'.
Also sometimes the first error is 'Privileged instruction' at the
same line. The error is not permanent but happens randomly and frequently.
It's on W2k and XP with BDE 5.01 and Paradox, D4, FR246 and FR254
(other Delphi/OS/FR-versions not tested).
I've already tried to change most BDE settings, but no luck.
I can reproduce it on a new and clean XP installation with nothing else
installed except a standard, full BDE installation and my application.
The strange thing is that it did not happen for a long time on my system
until I made and *reverted some changes to IDAPI.CFG thru BDE-Admin, now
it happens very frequently, and always after the application has loaded another
database (it doesn't matter which database was loaded just switching between
different databases seems to trigger).
Has anybody else ever seen something like that?
Regards,
Arno Garrels
In FR_Class.InitDataSet, somewhere in: CreateDS(Desc, DataSet, IsVirtualDS),
I get an AV at 4CDE4F9F in 'IDPDX32.DLL' read of address 0.
When I retry opening the report after that error I also get error
'Index out of bounds'.
Also sometimes the first error is 'Privileged instruction' at the
same line. The error is not permanent but happens randomly and frequently.
It's on W2k and XP with BDE 5.01 and Paradox, D4, FR246 and FR254
(other Delphi/OS/FR-versions not tested).
I've already tried to change most BDE settings, but no luck.
I can reproduce it on a new and clean XP installation with nothing else
installed except a standard, full BDE installation and my application.
The strange thing is that it did not happen for a long time on my system
until I made and *reverted some changes to IDAPI.CFG thru BDE-Admin, now
it happens very frequently, and always after the application has loaded another
database (it doesn't matter which database was loaded just switching between
different databases seems to trigger).
Has anybody else ever seen something like that?
Regards,
Arno Garrels