Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Cannot load MSXBSE35.DLL
Message
 
 
To
21/05/1998 13:51:40
Elyse Pomerantz
Dynamic Data Concepts, Inc.
Brooklyn, New York, United States
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
00100892
Message ID:
00100977
Views:
23
>A new client just got an error trying to install my program (I use the VFP Setup Wizard). The error is "Cannot load MSXBSE35.DLL." Has anyone else seen this? I've distributed a number of installation CD's already and no one else had this problem. My VFP5 application is developed on a Win95 computer. Does it matter if the application is being installed on a Win95 or WinNT machine?
>
>Thanks,
>Elyse

I have a similar error messages with MSXB3032.dll. You are the first person I've seen with a similar problem. For me it occurs randomly during installation, and I mean very random. I've tried every combination possible between WIN95 vs. NT, With and without MS Office, etc... Identically configured machines can have different results. I'm sure something must be different, but I haven't been able to narrow it down. (and I've been trying for quite a while now) This happens enough that we have started including an extra disk with the file MSXB3032.DLL on it. We copy this file into their windows/system directory and then it will install fine. This is disturbing, because it is on the installation disks and should copy in if it doesn't exist. However, sometimes the file is on their computer and we have to delete it to get the installation to work. (go figure) The only thing that doesn't get installed in our situation is the ODBC drivers that allow our application to interface with MS WORD. The only documentation I have found on the issue on the Microsoft web site was not for VFP. Apparently these files are used during the installation of MS products. I have heard of people having this message while installing other programs unrelated to VFP. I don't know if MSXB3032.DLL is related to MSXBSE32.DLL, but it seems as though they are. So here is a lot of information with no real solution, but at least we both know we're not alone. You may try including the file on your installation CD's so you can manually copy it into the Windows\System directory just in case. I was really hoping this would stop when we switched to VFP 5 but it doesn't look good. I just can't believe that so few people have had this experience.
Marcus.
Previous
Reply
Map
View

Click here to load this message in the networking platform