Par2: Multiple file DLLs, 32 bits and Name() attribute 1998-09-16 -- Paul Attryde I think the problem you're describing is the same one we faced when we moved our app from 16-bit to 32-bit. You have a DLL declaring a file, but the variable named in the NAME attribute is actually declared and exported from another DLL? It works fine in 16-bit, but if I remember correctly it's something to do with 32-bit being unable to do a double de-reference (now that everything can move about in memory it's not quite the same as 16-bit) Our solution was to declare and export the variable named in the NAME attribute in the same DLL as the file declaration. The code that initialises all the file name variables doesn't care which DLL the variable is exported from, it just needs to be in scope. You may have to play around and change the order of the DLLs, but it works fine for us. Scott Ferret adds that this may be a template problem. Printed April 29, 2024, 2:48 pm This article has been viewed/printed 35111 times. |