Member Avatar for abu taher

I make a setup file. I install it in another computer. When I run the application then show this error massage.

  • 4 Contributors
  • 4 Replies
  • 1K Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by rproffitt

Dani AI

Generated

As reported, the runtime 430 error means the program is calling a COM object that does not expose the interface the code expects. That is not an Access UI error — it is a COM/interface mismatch at runtime. and asked for more detail; the most useful diagnostics are the exact error line, any "MISSING:" markers from the VB6 project, and which OCX/DLL/ActiveX EXE the app relies on. is correct that simple packaging often misses dependencies; below is a focused checklist to find and fix the mismatch.

  • On the development side, ensure every ActiveX DLL/OCX used by the project is compiled with Binary Compatibility (Project -> Properties -> Component -> Binary Compatibility) against the last published binary, then rebuild. That preserves COM interfaces and avoids 430 after redeploy.
  • Open the VB6 IDE and look for any "MISSING:" references; resolve or update them and recompile.
  • On the target machine register all COM components explicitly. Examples:
regsvr32 "C:\Path\YourControl.ocx"
"C:\Path\YourServer.exe" /regserver
  • Use Dependency Walker (depends.exe) or ProcMon to spot missing system DLLs, and verify the correct database engine (Jet/ACE) or ADO/DAO provider is present if the app touches Access files.
  • As a short-term diagnostic, run a tiny VBScript that CreateObject()s the server to confirm whether the ProgID/CLSID responds.

Reproduce the failure on a clean VM, isolate the failing COM server with a minimal repro, then update the installer so it explicitly deploys and registers every OCX/DLL (or use a more capable installer). Following the binary-compatibility + explicit-registration path will resolve the majority of VB6 430 cases.

Recommended Answers

All 4 Replies

Member Avatar for Reverend Jim

You are going to have to give us more information.

Member Avatar for rubberman

This is not enough information. Please show what you have done.

Member Avatar for abu taher

I make the setup file by package & development wizard. Then I install it another pc (use setup file). When I run the exe file then show the error massage.

its a database application. Use Ms Access and vb 6.

Member Avatar for rproffitt

Ahh, now I see it. That old system required a lot of runtimes besides what VB6's packager would kit up for you.

I lost count of the broken bodies and minds when the author discovered they needed to install MS Access and a VB6 runtime to get their "simple app" to run.

The cost of their app was a big more than they expected.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.