[Anonymous]

I received a speedy and frank reply from Symantec:

>>>>
Thank you for contacting Symantec Online Technical Support.

Please note, the WinFax 10.02 SDK was not tested with Windows XP. There are no plans at this time for further development or udating of the SDK.

Sorry if that causes you any problems, but your answer might be to find another fax product that supports your VB DDE functionality on Windows XP.

Note: Many customers are saying that the SDK works fine with WinFax PRO 10.3

Please let me know if you have any additional questions.

Best regards,
xxxxxxxxx {name removed from post}
Symantec Authorized Technical Support
>>>>>

I assume that WinFax PRO 10.3 above really means version 10.03.

It’s good to know the direction we need to be prepared to take in the future. For now, we’ll keep using WinFax 10.01 in Windows XP — seems to work fine so far. We’ll just be prepared to switch to another product if and when we switch to an operating system that WinFax 10.01 no longer works on.

I must say I am disappointed with this decision, since the only reason we purchased WinFax in the first place was for the SDK, and we’ve invested a fair bit of development effort in integrating faxing and logging into our Microsoft Access/Oracle application. ??? I can only assume that Symantec has determined that the development effort required to update the SDK will not pay off in sufficient additional sales. Perhaps thought has been given to making the SDK a separate add-on that users pay extra for? When we last shopped for a faxing solution, we chose WinFax because it was by far the cheapest software that came with an SDK. I would think there would still be a market for a separate WinFax SDK.

Finally, I requested that Symantec add an item in their SDK knowledge base with the information in their response included. In the case of the SDK, developers who are using the SDK need to know that it is no longer supported so they can determine if they need to make plans to move to another product.

I must say I do find it curious that WinFax 10.03 seems to fix some of the problems with the SDK, as noted by several posts here. Perhaps Symantec did make some fixes here, but is not willing to go any further or make any promises of it working in the future? I have not tried 10.03 myself yet, but that may be an option in the future.

[redwebgeek]

Hi

I’m trying to learn to use vb.net and winfax.
I’ve tried

Dim pageObj As New wfxctl32.COleCoverPagesClass
pageObj = GetObject(“wfxctl32.COleCoverPagesClass”)
TextBox1.Text = pageObj.Count

and keep getting a “Specified Cast is not valid” anyone have any ideas for a realllllly frusturated person

[JohnD]

@redwebgeek wrote:

Hi

I’m trying to learn to use vb.net and winfax.
I’ve tried

Dim pageObj As New wfxctl32.COleCoverPagesClass
pageObj = GetObject(“wfxctl32.COleCoverPagesClass”)
TextBox1.Text = pageObj.Count

and keep getting a “Specified Cast is not valid” anyone have any ideas for a realllllly frusturated person

I don’t believe that is the proper syntax for the cover page object. check the coverpage object properties in the SDK User’s Guide (you can download a copy in the download section at http://www.getfaxing.com/download.htm

also there is a known problem with WinFax SDK where sometimes the cover.db file gets corrupt, this can also cause any calls to the coverpage object to fail. you’ll need to rebuild the cover.db file. There are a few messages in this forum regarding this.

[Author]

Posts