BorlandTalk.com

D Ray · Guest

I'm using Locate to check for duplicates during a database import that
involves hundreds of thousands to millions of records. The following
code is consistently generating a memory leak, and I'm wondering (a) if
anyone knows the cause of it (there seems to be some stuff in previous
posts about Variants generally, but I couldn't nail down anything
specific), and if not, whether anyone can suggest a workaround that
would be just as fast. (By the way I define FBN as FieldByName as a
shortcut in coding, and LocateArray and SearchOptions are defined
globally rather than within this function).

Thanks, in advance, for any suggestions....

if (!RemoveDuplicatesCheckbox->Checked)
return false; // just assume not a dupe.

LocateArray.PutElement (Imp->FBN("First Name")->AsString, 0);
LocateArray.PutElement (Imp->FBN("Last Name")->AsString, 1);
LocateArray.PutElement (Imp->FBN("Middle Name")->AsString, 2);
LocateArray.PutElement (Imp->FBN("Street Name")->AsString, 3);
LocateArray.PutElement (Imp->FBN("House No")->AsString, 4);
LocateArray.PutElement (Imp->FBN("Apt No")->AsString, 5);
bool RetVal = DM->MList->Locate ("FIRST NAME;LAST NAME;MIDDLE
NAME;STREET NAME;HOUSE NO;APT NO", LocateArray, SearchOptions);
return RetVal;

Mark Guerrieri · Guest

D Ray · Guest

Thanks for the suggestion -- after doing further reading, it seems the
help has had a lot of people confused on this for a long time; I've been
using the other form since BCB1, but have never had to deal with a
million or more records so hadn't picked up on the leak. At any rate, I
changed it to look like your code with one exception:

bool RetVal = DM->MList->Locate ("FIRST NAME;LAST NAME;MIDDLE
NAME;STREET NAME;HOUSE NO;APT NO", VarArrayOf(LocateArray,5),
SearchOptions);

Memory leak is gone.

Thanks a lot for the suggestion/cure.