Hi Marco & Co.,
Having recently upgraded to 3.4.3, I've been removing all my work-arounds for Object and LOB support, and in the process have discovered a new bug in TLOBLocator. I have a collection of LOB elements (strange but true). As I am processing each element, I create a new LOB Locator, then copy across the element using the Assign method as follows:
NewLOB.Assign(Obj.GetLOBElement(Index));
This works fine, except if the element is null (ie: IsNull = True), NewLOB is *not* null! Subsequently, code which calls NewLOB.Size (and I assume, other methods as well) fails (as the check for IsNull thinks the LOB is valid)
Somewhere later, when all the LOB Locators and Objects are cleaned up, I get AV's .... I haven't stepped through that code yet, but I guess it has to do with the above.
Having recently upgraded to 3.4.3, I've been removing all my work-arounds for Object and LOB support, and in the process have discovered a new bug in TLOBLocator. I have a collection of LOB elements (strange but true). As I am processing each element, I create a new LOB Locator, then copy across the element using the Assign method as follows:
NewLOB.Assign(Obj.GetLOBElement(Index));
This works fine, except if the element is null (ie: IsNull = True), NewLOB is *not* null! Subsequently, code which calls NewLOB.Size (and I assume, other methods as well) fails (as the check for IsNull thinks the LOB is valid)
Somewhere later, when all the LOB Locators and Objects are cleaned up, I get AV's .... I haven't stepped through that code yet, but I guess it has to do with the above.
