I'm having weird memory errors with an upsizing routine we are running at a client. The upsize works fine on a workstation (perhaps a little slow) and no problems are seen there. The issue starts when we try to run the program on a brand new top of the line server.

The server is a Quad Processor Compaq (unsure of speed). There's 4GB of memory and multiple RAID 5 arrays. What I'm worried about is the stability of NT4 and SQL with the large amount of memory. NT4 wouldn't even go in with 4GB, and we had to install with 2GB, do SP6a, and then put in the 4.

The error we get is SQLSTR.DLL Initialization Error. This occurs during the upsizing routine.

I've tracked down the DLL and found it to be an MDAC file. I'd like to just try a new MDAC version, but this is not an option.

So what does anyone know? Are we using too much hardware for the OS configuration we have? Does anyone have any experience with high power servers and weird errors? Is there anything that should be adjusted with VFP memory, such as FOREGROUND and BACKGROUND memory settings?

I'm really leaning toward a stability issue with SQL and NT4 at 4GB... but I don't know how to prove/test it. AND OF COURSE... the clients are blaming VFP. If I only had a dollar for everytime that happened!

Thanks all!

Shawn Burke