J
Jed
Does anyone know this...
I have an application that imports FM20.DLL. On my harddrive in the
Windows/System32 directory is FM20ENU.DLL. All works fine.
My customer in France has the French version of Office. She has FM20.DLL
and FM20FRA.DLL.
The problem is some of the controls don't show up. Then I had her copy
FM20ENU.DLL into her Windows/System32 directory, and now my application
shows those controls again.
I would have figured that it wouldn't matter which FM20???.DLL the user has.
The users localation would tell her which FM20???.DLL to use. As long as I
import FM20.DLL it should work. Her French MS Office works fine.
How does it know which FM20???.DLL to use? Does she have the wrong
FM20.DLL? Are they generally paired?
Thanks,
JedK
I have an application that imports FM20.DLL. On my harddrive in the
Windows/System32 directory is FM20ENU.DLL. All works fine.
My customer in France has the French version of Office. She has FM20.DLL
and FM20FRA.DLL.
The problem is some of the controls don't show up. Then I had her copy
FM20ENU.DLL into her Windows/System32 directory, and now my application
shows those controls again.
I would have figured that it wouldn't matter which FM20???.DLL the user has.
The users localation would tell her which FM20???.DLL to use. As long as I
import FM20.DLL it should work. Her French MS Office works fine.
How does it know which FM20???.DLL to use? Does she have the wrong
FM20.DLL? Are they generally paired?
Thanks,
JedK