If you contact support and it is determined that this is your error, you will
not be charged for the call. The charge will only be assessed if the
mentioned bug fix is not your issue.

There may be a way to alleviate the problem.

1. How big is the Hashtable you are loading (ie, how many records)?
AND, more importantly
2. How much memory is the Hashtable consuming?

If you are loading HUGE Hastables, you will overrun the 2 GB limit per
process. This should throw an out of memory exception, but I am not sure this
is 100%. If you think this might help, there are two potential solutions to
this issue:

1. Move your application to a 64-bit machine, which has a much larger
address size. Have not tested this, but it has been suggested.

2. Increase the amount of memory per process in the registry. NOTE: If you
go this route, make sure you do not lift the value so high that you go over
your machine memory limit (factor in overhead for OS and all services
running, as well).

If these suggestions offer no solice, I would consider calling MS support.
If it turns out to be MS's fault (you found a bug, either the one mentioned
or a new one), you will not be charged.

---

Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

***************************
Think Outside the Box!
***************************