Unable to complete order after item cancelled.

[Ginnys Attic]

I've just had a customer call as they ordered the wrong item and wished to cancel it. I went to the order selected the product and clicked cancel. All seemed well and Actinic reduced the item from 1 to 0 as expected but when we try and complete the order we get the following error:

Error in File C:\Program Files\Actinic v9\Invoices.rpt:
Error in formula <InclusivePrice>.
'Numbervar bCost := {OrderDetail.Price};'Division by zero.

We are unable to complete this order but Actinic does prepair the order shipped email everytime i try and complete the order. Does anyone have any ideas if there is a fix for this so we can complete the order?

[plantsforshade]

It's a bug, Actinic know about it and say they will fix it sometime, please read (the thread) all for the get around.

http://community.actinic.com/showthread.php?t=37252

Regards

Nigel

[Ginnys Attic]

Thanks for the help Nigel, looks like a venture in to the database is required :-(

[plantsforshade]

We just use the export order facility to force the order into the completed order tab, much easier.

Regards

Nigel

[Ginnys Attic]

I've managed to complete the order although i got the same error when it tried to print the invoice and i get the same error if i manually try and print the invoice. At least it's not sitting in the pending orders anymore which is better than nothing i guess although i would expect the customer would have liked there invoice as well

[TraceyG]

Hi Adrian,

I think your issue is slightly different to the issue in the other thread mentioned as you are getting an error. It would be useful for us to know why you are getting the 'division by zero' error so I suggest that you raise a support ticket (use the link in my signature) so we can get a snapshot and find out the cause.

[Ginnys Attic]

Thanks Tracey, support form submitted but i think i'll need to ftp the snapshot somewhere for you guys as they run at about 135mb

[Ginnys Attic]

In case anyone else has this problem i have had word back from support who say they can replicate the error and have esculated it to the dev team for analysis and will let me know. I assume this means it's a further bug within V9 and i'll post what they let me know as and when.