Page 2 of 2

Posted: Thu Jul 21, 2005 8:20 am
by chulett
I'll keep that in mind, Mr Duke. :wink:

Posted: Thu Jul 21, 2005 12:32 pm
by kduke
Mr. Craig

Come to think of it memory leak could not be your problem because of your error message. Something in a hash file blew up. Was your hash file over 2GB? Another thing might be a char(255) or 254 in your data or key. Is that possible?

Posted: Thu Jul 21, 2005 12:38 pm
by chulett
Nope, not over 2GB. And I really don't think there was anything funky in the data or keys for that matter. From what I recall, ran twice with the same data set and it cratered twice. Deleted the hash and ran a third time and all was golden.