Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 525
  • Last Modified:

Received error "ActiveX component can't create object" while calling WinFax.SDKSend in VBA

I've just upgraded to WinXP o/s from WinNT. My Access database which calls the WinFax (WinFax Pro version 10) SDK failed with a run-time error "ActiveX component can't create object". Because of this error, I've taken the following steps of action, yet the error remains:
1. Upgraded the database to Access 2002 from Access 2000.
2. Compiled the modules successfully.
3. Checked the library references - all are linked (no MISSING).
4. External library dlls modules are correctly registered with regSvr32.
5. Steps in Microsoft Knowledge Base 319841 have been follow through.
6. Checked to use the latest service pack and versions (DAO 3.6, ActiveX data object 2.8, OLE Automation, Winfax Automation Server, Symantec Winfax Pro Control)

Please advice; what is the solution?
 
The VBA line of code that caused the error #429 - "ActiveX component can't create object" follows:

    Set objWFXSend = CreateObject("WinFax.SDKSend")     '<---  Late Binding

Thanks,
Alice
0
AliceEng
Asked:
AliceEng
  • 2
1 Solution
 
jjafferrCommented:
Another user had a problem with WinFax, you can see it here
http://www.experts-exchange.com/Applications/Q_20942955.html#10752002

Please read the whole thread to get a better picture of what happened, and don't be decieved by the title.

jaffer

0
 
AliceEngAuthor Commented:
Hi,
Thanks for the reference. However, I've already uninstalled and re-installed WinFax Pro, same error exists.
Can anyone tell me if a later version of WinFax Pro SDK package (beyond v10.2) that will handle Windows XP OS complacently?
Regarding the environment of this application:
1. The Operating System is WinXP.
1. Front-end user interface is written in MS Access 2002.
2. Back-end database is SQL Server 2000.
3. Application uses ODBC connection and DAO (it is not an Access Project, and doesn't use ADO)
4. A front-end Access Report event procedure fires a call to the VBA Fax module passing the report image along with the fax#, title, description, cover page, and other required fax elements.
5. The front-end Access VBA function calls the Symantec SDK DLL objects and initiates a Fax session. When the code CreateObject("WinFax.SDKSend") is executed at run-time, the error handler returns the error# 429 with the message “ActiveX component can’t create object”.

Regarding the history:
1. At the days of WinNT O/S, MS Access 2000, and SQL Server 2000, the Fax application operates normally, slow at time, but completes successfully and automatically in sending more than 90 faxes (= 90 reports) to different fax numbers across the country.
2. Now under WinXP O/S with the same application environment as stated above, the system errors out.  Users have to manually print-preview an Access Report and print it to the Fax device instead of the printer.  With the manual method, users must repeat the report print process 90 times. Frustration mounts; it takes days instead of minutes to perform the same function.

Any help will be most appreciated,
Alice.
0
 
jjafferrCommented:
Hi Alice
I don't know how much this will help, but its worth reading,
I was answering another question regarding dialog browser,
when I gave the asker the code and later I sent a working mdb,
s/he kept getting the same error as yours: error# 429 with the message “ActiveX component can’t create object”
http://www.experts-exchange.com/Databases/MS_Access/Q_21078927.html

So this makes me think:
There must be an ActiveX component that was installed on the WinNT pc which is not installed on the WinXp pc,
and it doesn't show in the Reference, but WinFax depends on.

Did you mean to say that users are still using WinFax but manually?
If you change the default printer to the Fax device and print, will that solve your problem?
check in www.lebans.com for a default printer code,
which will change the default printer in your mdb, then revert to the original when you quit.

jaffer
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now