Will the update release be delayed?

Because this update contains tax changes that are effective July 1st, the update will be going out to customers as planned.

Thanks Kathleen, do you know what time today we can expect it? Will there be a followup patch?

We are began releasing to customers yesterday, and will continue to release through 6/27. Right now we have not determined if this will be fixed in another update (patch) or if we will be fixing this with the next release in October.

Thanks. I received it for my SAN license, but not at the school where I work, where we are using Sage 50 Premium.

Hi Kathleen, Our company does about 4,000 sales invoices a year, and most from recurring transactions.

"When using the keyboard and typing a letter to bring up any new recurring transaction I get an unhandled exception error"

It isn't clear whether this will affect recurring transactions that were created before the update, or whether the 'new' refers to all new transaction that are from a recurring transaction.

So long as the mouse will work, or if the unhandled exception won't cause data loss, we're probably OK, although there will be considerable grumbling among the troops.

Having the feature to add a link to a file / document from a transaction will be a major bonus for us, so we'll update even though there are no tax changes for our province

Hi Randy, great points! This won't impact the actual recurring transactions, past or future. It only occurs in the "recall recurring transaction" window where you are selecting the recurring transaction for your sales invoice. If you use the mouse, you will not receive the error message. If you use your keyboard, you will receive the error mesage, but can click Continue and move past it. This is not at all damaging data, but we do realize that it has the potential to impact the workflow of many of our customers.

Thanks Kathleen,

I'm clear under what circumstances we'll see the error, but what still isn't clear to me, is whether the issue will occur with:

1 - only prior recurring transactions created using the 2017.1 release or older, or

2 - only new recurring transactions created in the 2017.2 release

3 - *all* recurring transactions stored in Sage 50, whether newly created in the 2017.2 release, or already existing from 2017.1 or earlier.

Could you please clarify that?

Any recurring transaction that appears in that window will be impacted no matter when it was created. It isn't the transaction itself that is causing the error.

This "error message" hasn't appeared in my Windows 7. However, upon opening a recurred transaction, every time I change to a different customer or vendor, the Payment Method changes to "Pay Later" instead of staying in the recorded one. Anyone knows how to stop this from happening?

Louis Kam said:

Payment Method changes to "Pay Later" instead of staying in the recorded one

There is much discussion on these forums regarding this feature in release 2017.0 + (2016-10?), such as this thread starting about 8 months ago:

https://sagecity.na.sage.com/support_communities/sage_50_accounting_ca/i/accounts_payable/change_payment_method_to_a_pin__get_it_out_of_default_vendor_options

Autocorrect and 'Teen Talk' have 'off' switches.  The feature was non-optional and has no 'off' switch.

This thread's discussion is in regard to a minor, specific bug with an easy work-around for the June 2017 release number 2017.2 of Sage 50 Canadian. 

Thanks for the link, Randy.
This issue only come to my attention recently so I thought it is from V2017.2 update.

HI Kathleen. I think the customer base who uses these recurring transactions need it resolve sooner then October please and thank you.

October is way too far

Agreed, October is too long. This really slows things down.

I'm starting to get used to it, like I've gotten used to the other clumsy work-arounds for prior years' interface bugs and poor designs.

RandyW I am not sure if I should be liking or disliking your comment :-(

RandyW I am not sure if I should be liking or disliking your comment :-(

I'm not sure either. I'd probably be much more satisfied with the interface in Sage 50 2017 if I had never seen Simply Accounting 2007.

On the other hand I wouldn't be as pleased with the robust MySQL multiuser back end performance of Sage 50 2017 if I had never used Simply Accounting 2007.