Forum Replies Created
-
Posts
-
Let me know if you hear anything back from Symantec on this issue.
I understand that the 10.02 upgrade simply fixes compatibility with Outlook XP integration, support for multiple users in XP? (not sure about that) and updated macros with new digital certificates. (which I see there are reports of problems)
Not sure if there were any bug fixes from previous releases.the same Access project worked fine with 10.0 in XP. I didn’t touch it, then I installed 10.02, and today found it not working.
I did not have 10.01, it was withdrawn from the symantec site soon after put there, I did not catch it.
Some user reported in symantec forum that though the web page wants about โ for the upgrade, he called customer support and been offered the upgrade for บ plus บ shipping.
Amazingly, Symantec does not tell about 10.02 anything but “compatible with XP”, no further details, not a single fix. I even called their sales, and they said they don’t know either.
(Edited by vrapp at 2:09 am on Nov. 24, 2001)
Hi vrapp, does the same thing happen with 10.0 or 10.01 with Windows XP , or is it specific to 10.02 and Windows XP?
Sorry I don’t have 10.02 to try this. Unfortunately, it is not a free upgrade offered by Symantec.
In Word, PrintToWinfax works, but it’s because that macro in its current version does not use the COM object, all it does is changing the printer, printing, changing printer back. However, WinFaxMerge does use it, and does fail. I just un/reinstalled 10.02, to no avail.
I posted this in symantec support sdk forum as well, will see…
I’ll have to check that out, I have not tried it with Windows XP. Does the Word or Excel macros supplied with WinFax PRO 10.02 work? because it uses PrintFromApp in the code as well…Don’t have a XP machine here handy to test, but should within the next week or so.
I should also mention that the file you attach must be able to automatically print to the WinFax printer driver (so the conversion process can be accomplished without any user interaction)
the file you attach must have an association in windows so it can print. One way to test this would be to right-click the file in Windows Explorer and select Print. If it prints without any dialog boxes, you will be able to attach with WinFax.that is a little tricky, you can use the AddAttachmentFile command to do the conversion, but you will not know how many pages it will be once completed.
I tried that but the EntryID was never ready… even though the fax was completed and sitting on the RightFax server ready to go.
I opted for the LeaveRunning() solution instead.
Thanks,
AlexYeah I know it’s a lot of code. The For Next loop is to see if any error will trigger before sending. Sort of a dry run. The error log errors out after 20 mins in the Do While .IsEntryIdReady(o) <>1
DoEvents
Loop
Before I put the break a 20 Mins it would sometimes go 40 mins +.
Does modem pooling have any bearing on this? Should Winfax be reinstalled? Maybe the registry is messed up? They ran Rebuild.bat and sometimes have this same problem.Thanks
no problem . if you had a question, and found the answer yourself please post your solution. It may help others in solving the same problem.
Thats a lot of code to review…i expect it is a problem with some of the for/next loops.
you might want to hard code some of the data and see if you get the same problemsQuote: from bucco on 8:46 pm on Nov. 14, 2001
I’m trying to create a module in Access 97 that sends faxes to different customers in the customer table. I’m using the Windows NT operating system. Can anyone direct me to a sample module?Access 97 (i think) uses VBA. If you look at the Word VBA sample, that might help you out. The sample is located in the DOWNLOADS section of the Web site.
