VB项目中Crystal Report报Error 20728-F且无法注册crpe32.dll求助

Hi there, let’s work through this frustrating Error 20728-F issue you’re facing with Crystal Reports in your VB6 project. Legacy VB6/Crystal Report setups on Windows 10 often run into compatibility and registration hurdles, so here are targeted steps to resolve the crpe32.dll registration failure and underlying error:

1. Ensure DLL Version Match #

First, confirm you’re using the exact version of crpe32.dll that matches your Crystal Reports installation and crystl32.ocx control. Randomly downloaded DLLs from third-party sites almost never work—they need to align with the Crystal Reports version you installed (e.g., 8.5, 9.0). If you don’t have the original DLL from your Crystal Reports setup media, track down a runtime installer for your specific version (not just standalone DLLs).

2. Use 32-bit regsvr32 for Registration #

Since VB6 is a 32-bit application and Windows 10 is 64-bit, you must use the 32-bit version of regsvr32.exe to register crpe32.dll:

• Copy crpe32.dll to C:\Windows\SysWOW64\ (the 32-bit system directory)
• Open Command Prompt as Administrator (right-click → Run as administrator)
• Run this command:

  C:\Windows\SysWOW64\regsvr32.exe C:\Windows\SysWOW64\crpe32.dll
  

This avoids permission issues and ensures the 32-bit DLL is registered correctly for your VB6 app.

3. Install Full Crystal Reports Runtime #

Don’t rely on copying individual DLLs—install the complete Crystal Reports runtime package for your version (e.g., Crystal Reports 8.5 Runtime for VB6). This installs all required dependencies (not just crpe32.dll) and handles proper registration automatically. Many registration failures happen because missing supporting DLLs aren’t present.

4. Verify Control and Reference Setup in VB6 #

• Ensure crystl32.ocx is also registered using the same 32-bit regsvr32 tool:

  C:\Windows\SysWOW64\regsvr32.exe C:\Windows\SysWOW64\crystl32.ocx
  

• Open your VB6 project, go to Project → Components, and confirm the Crystal Reports control is checked (and matches your installed version). Remove any outdated or mismatched references and re-add the correct one.

5. Bypass System Directory Restrictions #

If registering in SysWOW64 still fails, try placing crpe32.dll and crystl32.ocx directly in your VB project’s execution directory (where your compiled EXE will run). Register the DLL from this location instead:

C:\Windows\SysWOW64\regsvr32.exe "C:\Path\To\Your\Project\crpe32.dll"

Windows 10’s UAC often restricts modifications to system directories, so using your project’s local folder can bypass these issues.

6. Adjust Compatibility and Permissions #

• Run VB6 IDE or your compiled EXE as Administrator (right-click → Run as administrator) to avoid permission errors when accessing registry or system resources.
• Set the VB6 IDE/EXE to Windows XP SP3 Compatibility Mode: Right-click the executable → Properties → Compatibility tab → Check "Run this program in compatibility mode for" and select Windows XP (Service Pack 3). Old Crystal Report versions often behave better with this setting.
• Ensure your Microsoft Access database file and its parent folder have read/write permissions for the current user—report loading failures due to database access can trigger Error 20728-F as well.

7. Double-Check dwmapi.dll #

Even though you registered it successfully, confirm you’re using the 32-bit version of dwmapi.dll in C:\Windows\SysWOW64\ (not the 64-bit one in System32). VB6 will only load 32-bit DLLs, so mismatched architecture here could still cause issues.

Give these steps a try in order—starting with version matching and correct registration is key. Let me know if any of these resolve the error or if you need further clarification!

内容的提问来源于stack exchange，提问作者user3636388