Login
`
Templates, Tools and Utilities
|
||
Add a comment to an Icetips ArticlePlease add your comments to this article.
Please note that you must provide both a name and a valid email address in order
for us to publish your comment. Comments are moderated and are not visible until they have been approved. Spam is never approved!
Back to article list Search Articles Add Comment Printer friendly Direct link 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.
Today is December 3, 2024, 11:55 am This article has been viewed 35199 times.
|
|