XP Pro effecting coding?

[cranebill]

Is it possible for XP Pro to effect the way one program talks to another? I have a db written in access which is supposed to open up winfax and send faxes automatically. Now i have been working on this for 3 days and finally installed Office XP and Winfax 10.02 on a machine that is only running windows 98 and the coding works fine... is there a way to fix this, or does anyone have any ideas?

Bill

 

[vbajock]

What line of code is failing? What is the error message?

 

[cranebill]

It doesnt have error messages at all actually... i am running XP Pro, Windows XP Pro, and Winfax 10.02. When i run this code its supposed to send faxes automatically, by opening the winfax send screen, filling in the appropriate data, ie name, fax number, etc. and sending. Well in XP it opens up the send screen and fills out nothing automatically. It does attach the report though. When i installed the same applications on Win 98 it runs perfectly. Im kinda stumped here, if it were just me using it i would throw up a dummy machine to run this temporarily, but more than just me needs it.

Bill

 

[vbajock]

I checked out the version of Winfax and it does support XP, so the problem must be in Access. Does the code that fills the screen in use Sendkey commands or is it using DDE ? I have heard that DDE is not supported on XP machines.

 

[cranebill]

I really dont know to be honest, here is the code from the form:

Option Compare Database
Option Explicit

Private Sub cmdFax1_Click()
On Error GoTo HandleError
If Programming_Mode Then On Error GoTo 0

'----

Dim strPhNmb As String
Dim strAreaCode As String
Dim strPersonTo As String

Dim intHold As String
'------

'Set Variables
strPersonTo = Me.TxtTo
intHold = Me.grpHold

Select Case Len(Trim(Me.txtFaxNmb))
Case 10 ' has Area Code
strAreaCode = Left(Me.txtFaxNmb, 3)
strPhNmb = mID(Me.txtFaxNmb, 4)

Case 7 ' no area code
strAreaCode = ""
strPhNmb = Trim(Me.txtFaxNmb)

Case Else
MsgBox "Bad Phone Number - we are looking area code and number or number only."
Exit Sub
End Select


'-- If you want to take the code out of the form copy from here down and set the below variables
'strAreaCode = "913"
'strPhNmb = "5557515"
'strPersonTo = "Larry Gordon"
'intHold = 1


'------------- Start Conversations with WinFax
Dim objWFXSend As New wfxctl32.CSDKSend '<--- By using this line you get the pull down list of methods (Called Early Binding)
' To use this line you need to have 'WinFax Automation Server' Checked in your references
' To Check 'WinFax Automation Server' open a module then from the menu
' Tools | References | and find 'WinFax Automation Server' - If you can't find it
' Try browsing for C:\Program Files\Symantec\WinFax\wfxctl32.tlb
' This will also Open the 'WinFax Controller' in your task Bar Tray

'Dim objWFXSend As Object '<--- If the above line give you problems use these two lines (Late Binding)
'Set objWFXSend = CreateObject(&quot;WinFax.SDKSend&quot



With objWFXSend


'Add 1 or more Recipients
.SetHold (intHold)
.SetCountryCode (&quot;&quot
.SetAreaCode (strAreaCode)
.SetNumber (strPhNmb)
.SetTo (strPersonTo)
.SetCompany (&quot;Test Company&quot
.AddRecipient ' You Can Add Multiple Recipients


'Cover Page
.SetSubject (&quot;Test Subject&quot 'If the next 2 lines are not sent to win fax there will be no cover page
'.SetCoverFile (&quot;C:\Program Files\SYMANTEC\WinFax\COVER\My_Cover.CVP&quot 'If a CVP (Cover Page) file is previded - your Cover page will print
.SetCoverText (&quot;Test Cover Text&quot 'If this line is sent without 'SetCoverFile' a quick Cover page is sent.


'1= shows progress screen 0= does not Show screen (1 default)
.ShowCallProgess (1) '<---- Notice the 'r' missing this works in WinFax 8 & 9
'.ShowCallProgress (me.grpProgressScreen)'<---- Works only in WinFax9

.SetPrintFromApp (1)
.Send (0)
DoCmd.OpenReport &quot;rpt_Is_Setup_to_Use_WinFax_as_Printer&quot;, acViewNormal
.done

End With

objWFXSend.LeaveRunning ' If we started WinFax with 'Dim objWFXSend As New wfxctl32.CSDKSend' this will leave it running.

'----

ProcedureDone:
Exit Sub

HandleError:
MsgBox Err.Description, vbCritical, &quot;Error &quot; & Err & &quot; in cmdFax1_Click&quot;
Resume ProcedureDone


End Sub '----------------------------------------

Can you tell from this?

Bill

 

[vbajock]

Have you checked to see if
C:\Program Files\Symantec\WinFax\wfxctl32.tlb
exists in this directory?

 

[cranebill]

I looked and that file was not in that location, so i copied it there to see if that would make a difference, it did not. I then deleted that and opend up the reference for the module for WinFax Automation to see where it was pointing. It was pointing at that file in the C:\Program Files\Winfax directory.

Bill

 

[vbajock]

Did you reboot the computer after you copied it to the correct location ?

It is DDE code. I'll get back to you in a few hours after a check a couple of things. I am wondering if you have to register any DLL's for this to work. IN the mean time, you might want to go thru all your code and see if all the files that have hard-coded paths are actually in those paths.

 

[cranebill]

Ok i appreciate all the help .

Thank you

 

[vbajock]

Ok, I looked at an old DDE program I wrote about three years ago. It has a reference to OLE Automation. If you click Tools, References, you can check this reference. If it is not there, add it and click Debug, compile, and save.
You might have to do a support thing with Symantec, a fate worse than death, if this doesn't work

 

[cranebill]

OLE Automation was already referenced so i must now go sit in a corner and rot lol

Thank you for trying though

Bill