Has anyone else noticed that the default Pre-Season Letter shows the Final date for RRSP contributions is March 3rd whereas it should be March 2nd in these two specific 2025 templates:
The dates are accurate in the other templates, but need correcting in these two templates. It’s an easy fix, but something to be aware of if you are still sending out these letters.
I can confirm the same incorrect dates in the Pre-season letters.
I use the post season letters for the prior year (2024) and the dates are all correct for those.
Thanks @kozakworld @grangers2016 I will get those corrected for the next release.
@elizabeth My pre-season letter doesn’t even work - the system crashes every time. This new design is frustrating!
Title: Something is not quite right…
Message: TaxCycle has encountered an unexpected problem and was unable to complete this task.
Please call \*\*1-888-841-3040\*\* for assistance with this error.
Details: TaxCycle 15.0.60436.0
System.ArgumentOutOfRangeException Index was out of range. Must be non-negative and less than the size of the collection. (Parameter ‘index’)
Source : System.Private.CoreLib
at System.Collections.Generic.List`1.get_Item(Int32 index)
at DevExpress.Office.UniqueItemsCache`1.get_Item(Int32 index)
at DevExpress.XtraRichEdit.Model.Paragraph.get_MergedParagraphFormatting()
at DevExpress.XtraRichEdit.Model.Paragraph.get_RightToLeft()
at DevExpress.XtraRichEdit.Commands.Internal.EnhancedSelectionManager.ShouldSelectToTheEndOfRow(RichEditHitTestResultCore hitTestResult)
at DevExpress.XtraRichEdit.Mouse.MouseCursorCalculator.CalculateCore(RichEditHitTestResultCore result)
at DevExpress.XtraRichEdit.Mouse.MouseCursorCalculator.Calculate(RichEditHitTestResultCore hitTestResult, Point physicalPoint)
at DevExpress.XtraRichEdit.Mouse.DefaultMouseHandlerState.OnMouseMoveCore(PortableMouseEventArgs e, Point physicalPoint, RichEditHitTestResultCore hitTestResult)
at DevExpress.XtraRichEdit.Mouse.RichEditMouseHandlerState.OnMouseMove(PortableMouseEventArgs e)
at DevExpress.Utils.MouseHandler.HandleMouseMove(PortableMouseEventArgs e)
at DevExpress.Utils.MouseHandler.OnMouseMove(PortableMouseEventArgs e)
at DevExpress.Services.Implementation.MouseHandlerService.OnMouseMove(PortableMouseEventArgs e)
at DevExpress.XtraRichEdit.Internal.InnerRichEditControl.OnMouseMove(PortableMouseEventArgs e)
at DevExpress.Xpf.RichEdit.RichEditControl.surface_MouseMove(Object sender, MouseEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.MouseDevice.Synchronize()
at System.Windows.Input.InputManager.HitTestInvalidatedAsyncCallback(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
I had the same issue (sort of) last year. I just could not open either pre/post season letters without Taxcycle freezing solid.
Sarka and I, tried to diagnose possible cause(s) for about a month with no success.
One thing that did work though was, if I right clicked on pre/post season letter and “print”, it would print - amazingly after that, both letters would be available within Taxcycle with no issue.
From what I could make out as cause of error/freeze, was older personal templates in Windows folders. Worked with that all last tax season. Never could find cause of issue.
This past July, I purchase, a new laptop Windows 11 and transferred data from old one to new. Installed newest version of Taxcycle and … same issue.
This week, got really annoyed with this and completely removed Taxcycle And all associated templates etc… from System ( see my previous post). Then did a complete re-install. Worked like a charm. Only thing I had to re-create new templates.
Try the right click/print see if it works.
