The problem is when I run the 'VB SDK Sample.exe' I get the following
error.
'Componet 'Tabctl32.ocx' not correctly registered: File is missing or
invalid'
I bought version 9.0 thinking this might be solved or atleast some Access
Code would be on the CD. However when I run 'SDKSend.exe' I get the same
error.
Two questions:
1) Where can I get Tabctl32.ocx, I've looked for it on microsoft's ftp file
site and your site and can not find it.
2) I see a lot of Access Questions on this news group. Is there any place
on the net with an Access example using automation with WinFax. I
personally have over 20 apps using Access to WinFax using DDE, why are
there no Access examples using WinFax Automation code out on the web or on
compuserve.
Thanks for any help in advance
Larry Gordon
Business & Computers
TABCTL32.OCX is the 32bit Active X Tab-Control included with Visual Basic
5.0+ (and most likely other Visual Studio applications) Since this is a
Microsoft file, I am unable to post or distribute this file. Please check
with Microsoft regarding obtaining this file.
if you have the file, but the error is refering to registration, you can use
the REGSVR32 program in the WINDOW\SYSTEM directory to register this OCX
from a DOS prompt
ie: C:\WINDOWS\SYSTEM> REGSVR32 TABCTL32.OCX
Hope this helps,
Sincerely,
Eric C [Symantec]
Online Services, Symantec Corporation
For Technical Support:
WinFax: http://service.symantec.com/winfax/
Talkworks: http://service.symantec.com/talkworks/
To Download Updates & Patches:
http://service.symantec.com/winfax/files_winfax.html
For a list of compatible modems for WinFax and Talkworks
Talkworks: http://service.symantec.com/twk8list.html
WinFax : http://www.symantec.com/winfax/index_winfax80.html
Need an upgrade? Have WinFax LITE, 2.0, 3.0? For a special price click...
http://shop.symantec.com
Please continue to post your messages to these discussion groups as we do
not provide support through private E-Mail.
Larry Gordon >> << wrote in message
<01bdeb08$653ffd00$67d696ce@larry-266>...
Thanks
Larry
Eric C [Symantec] <eca...@symantec.com> wrote in article
<6ur3jd$pje$1...@service.symantec.com>...