Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
User has wrong Ctl3d32.dll
Message
From
06/04/2000 11:58:17
 
 
To
06/04/2000 09:38:10
Jerry Tovar
Dana Corporation Dana It
Maumee, Ohio, United States
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00354275
Message ID:
00356332
Views:
11
I think that I had a 3rd party tool, a long time ago, that used it. Can't remember if it was Clipper or FoxWin.

As far as I know VFP does not use it. I do know that none of my apps use it.

In an earlier message I mentioned Netware. I believe it will recognize/use it if it's installed but I don't believe it has to have it to run.

Check it out on your own computer. Rename the file and run your programs to see if there are any problems.

As far as the required distribution files for your program are concerned, search in help on "distribution".

>Does "ctl3d32.dll" need to be distributed to run a VFP6 application? If not, I'll remove it from the setup. Wise7 automatically includes this file as part of the VFP6 runtime setup.
>
>If it is needed, I can test for which version of Windows a user has and install the correct file durring setup.
>
>Is there a list of runtime files that need to be distributed with a VFP6 application?
>
>Thanks for your help
>
>
>>This makes a little more sense now. You are including the NT version with your program even though it is apparently not needed.
>>
>>Another program on this users Win9x computer recognizes the ctl3d32.dll and tries to use it, but, it is the NT version. Your other users are not failing because they do not have a program on their computers that recognized and tried to use the dll.
>>
>>If the renaming suggestion doesn't work, you might have to send him the Win9x version (it should be on your MSDN CD, remember there are two). The original on his computer should be deleted before he copies the new one. This should fix his problem.
>>
>>Apparently, your program does not need the dll, so it should be removed from your setup disk(s). Or, include the Win9x version. Of course, if some of your users are running your program under NT, then you have another problem don't you? ....NT trying to use the Win9x version!
>>
>>I think you have entered into a world called "dll hell". Good Luck.
Previous
Reply
Map
View

Click here to load this message in the networking platform