Icon View Incident Report

Serious Serious
Reported By: Heiko Knuettel
Reported On: 8/8/2008
For: Version 2.01 Build 4
# 2751 Loading More Than One Instance of an External Module Can Cause Module Load Failure

At application startup, I open a disk- and a memory database, and then copy the stored functions from the disk database to the memory database, so that I can use them later in the memory database context e.g. for a "create table as...".

That works fine with internal SQL/PSM functions.

But when using an external function, in this case flagset(value, flagno: Integer):Boolean, a simple function that just checks if a bit in a integer is set, I have some trouble.

When executing the query "select * from diskdb.table where flagset(flags, 2)=false" in the disk database context (DataBaseName := 'disk'), I get the correct result set.

But when executing the same query (with the diskdb qualifier) in the memory database context, I get an empty result set.

Comments Comments
This issue was caused by the external module creation code not ensuring a unique component name for the external module instance, and can also occur with multiple loads of text filters, word generators, or migrator modules. You must make sure to recompile any external modules, text filters, etc. that are experiencing this issue with 2.01 B5 in order to correct this issue.

Resolution Resolution
Fixed Problem on 8/15/2008 in version 2.01 build 5

Products Affected Products Affected
ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial