I have successfully designed an Order Confirmation to fax to our customers, but I'm having difficulty figuring out how to choose options so that the fax number is formated properly.

All of our fax numbers are entered as follows:

1-415-821-3786

All start with a "1" unless they are international fax numbers. I even use the 1 and 415 for local fax numbers.

I noted in the Fundamentals book page 7-8 that

The fax function automatically adds a 1 to the beginning of all long distance numbers unless that number begins with a 1 or 0 already.

Well, our numbers start with 1 or 0, but I find that the fax queue shows the number to dial (per above example) as

1-14158213786

I do have a prefix of 9, stipulated, but that's all.

Suggestions?

Robert

Hi Robert,

We'll take a look. Perhaps that part of the scenario about not adding the 1 prefix when the fax number already starts with a 1 or 0 is not being adhered to.

If it is mission critical to get the faxes out, the fax numbers could be edited to remove a 1, either on the faxes in the queue or on the customer record.

However, there are modifications you can do. Under the Fax menu, there is a choice called 'Long Distance' that allows you to create custom rules in the case where you have 10-digit local dialing (ie a 10-digit number should not have the 1 prefix). From the Long Distance function, you specify your local area code and also all area codes/exchanges that require different rules to the default rules mentioned above. Such as 10 digit numbers that don't require a 1, or 7 digit numbers that require your local area code but not other prefixes.

Also, as you likely already use, the Fax Setup allows you to put in prefixes such as 9 for dialing outside.

I did setup the prefix 9 with no problems.

Back to the faxing rules . . . we have had a 1-XXX-XXX-XXXX format in use since day one. I would prefer not changing it if possible. For domestic customers (the vast majority of our customer base) that is an eleven digit number, always starts with a 1, and has hyphens.

Your reply says "Adagio by default automatically prefixes a 10 digit fax number with a 1" whereas the manual further stipulates "unless that number begins with a 1 or 0 already". Ours do start with a 1.

Does your post negate the manual or am I missing something?

Thanks
Robert

Sorry - I edited my initial post and you probably saw the unedited posting first.

We'll take a look. I've been told nothing should have changed in this area, but...

Are you using Formatted or Unformatted phone numbers in AR? This might make a difference. And can I confirm that you actually type in the hyphens into the fax number?

Thanks for your reply - I must have been looking at the unedited version. We are using unformatted telephone and fax numbers and we are putting in the hyphens.

The original concept was to present a number exactly as it would be dialed by a user - makes it easy to use with an autodialer and our fax server.

Robert

Hi Robert,

Thanks for identifying an issue that has existed in the product for over 5 years!

Apparantly, we aren't correctly dealing with telephone numbers that are prefixed with a one and a zero and have dashes as the separators.

Here are the choices to proceed:

• Export the customer number, name and fax number to Excel and remove the embedded dashes in the number. Import the resulting Excel file back into Adagio. (NOT recommended as it will make the telephone numbers very difficult to read.)
• Export the customer number, name and fax number to Excel and extract off the "1-" that preceeds each number. Import the resulting Excel file back into Adagio and then use the fax 10 digit dialing rules to get the right prefix assigned. (Some amount of work but will get you up and running pretty quickly.)
• Wait for us to fix the issue (perhaps 2-3 months before an official release, although we might be able to get a Hot Fix to you sooner.

Sorry for the inconvenience.

Andrew,

My role in the Accpac world hasn't changed now that I'm in the Adagio world - I just need a rofl icon here on the forum.

Seriously, thanks for looking into this and letting me know so quickly that this is an issue, as well as the serveral work arounds to use. I'll look forward to that hot fix when available and mull on how to handle in the meantime.

FYI, I was also playing around with the email function and found that my McAfee virus scan was preventing me from emailing on my workstation. This may be a known conflict, but thought I'd mention it anyway.

Robert

Hi Robert,

We have the same email scenario in our office, as we also use McAfee. The solution is to create an exception in McAfee to allow the Adagio program executable to do it's thing.

From the VirusScan Console, edit the properties of Access Protection.
Edit the proctection option 'Protect mass-mailing worms from sending email'.
In the field 'Processes to exclude', enter all the Adagio applications you wish to email from, such as oewin.exe, crwin.exe, and so on.

Hi Robert,

A fix for OrderEntry may be available sooner rather than later. It's probably not worth making any changes to your data.