I'm getting the below error when trying to create a summary value based on the sum of two other columns within the same group.
Basically, the calc is simply the sum(field1) - sum(field2). The formula compiles fine. The error occurs at the very end when the grid loads its data - meaning I can briefly see the grid populate (rows and tree view briefly appears) and then the error occurs.
I've attached some screen shots for your enjoyment. I have temporarily set the calcmanager to "Manual" to demonstrate that the regular calcs work fine during runtime. However, if I set it back to Sync or Async the error occurs.
at Infragistics.Win.UltraWinGrid.RefSummaryValueCollection.RefSummaryValueCollectionEnumerator.MoveNext() at Infragistics.Win.CalcEngine.RangeCalcInfo.EvaluateNextRow() at Infragistics.Win.CalcEngine.UltraCalcEngine.Evaluate(Int64 ticks) at Infragistics.Win.CalcEngine.UltraCalcEngine.Recalc(Int64 ticks, Boolean isStartOfRecalcOperation) at Infragistics.Win.UltraWinCalcManager.UltraCalcManager.ReCalcInternal(Int64 ticks) at Infragistics.Win.UltraWinCalcManager.UltraCalcManager.ReCalc(Int64 millis) at Infragistics.Win.UltraWinCalcManager.UltraCalcManager.onTimerTick(Object sender, EventArgs e) at System.Windows.Forms.Timer.OnTick(EventArgs e) at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.Run(Form mainForm) at BOJAppFrameworkShell.Program.Main() in C:\Documents and Settings\mnewmister\My Documents\Visual Studio 2010\Projects\BOJAppFrameworkShell\BOJAppFrameworkShell\Program.cs:line 24 at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args) at System.AppDomain.nExecuteAssembly(RuntimeAssembly assembly, String[] args) at System.Runtime.Hosting.ManifestRunner.Run(Boolean checkAptModel) at System.Runtime.Hosting.ManifestRunner.ExecuteAsAssembly() at System.Runtime.Hosting.ApplicationActivator.CreateInstance(ActivationContext activationContext, String[] activationCustomData) at System.Runtime.Hosting.ApplicationActivator.CreateInstance(ActivationContext activationContext) at System.Activator.CreateInstance(ActivationContext activationContext) at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssemblyDebugInZone() at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart()
Hi,
mnewmister said:Hmmm.... I have the 17-OCT-2010 release (vol 3). The timing of the discussion in that particular post kind of gave me the impression that it wasn't included.
The fix is not included in the October release. My very first reply on this thread was that you should get the latest service release. I posted a link with instructions on how to get it. Your next reply was that you "Just got the latest version and installed...same problem." So I have been operating under the assumption that you meant service release there.
Did you get the service release?
Thanks Mike.
>>I checked it out and the bug reported in that case was fixed. So the latest service release should contain the fix for that issue.
Hmmm.... I have the 17-OCT-2010 release (vol 3). The timing of the discussion in that particular post kind of gave me the impression that it wasn't included.
I will wait a couple of days for the newest service release before I create an sample.
Thanks again...
Hi Mark,
mnewmister said:Searched this site and found a couple of other similar posts - one with a case number: CAS-53752-WM7JTL. Has this case been resolved? Ironically, his last post was a day after the latest release dated 17-OCT-2010 so even if it is fixed I doubt it made it into the latest release.
I checked it out and the bug reported in that case was fixed. So the latest service release should contain the fix for that issue. So if you are using the latest service release and you are still getting the exception, then your issue must be different than the one reported in that case. If that's the case, then we need to be able to reproduce this new issue so that we can get it corrected. Are you able to reproduce the exception in a small sample project and post it here?
BTW... there is another service release which is just about to go out. It might be available as early as tomorrow. So you may want to wait a day or two and see if the new service release is any better before you spend any time creating a sample.
Here's some more info...
I put a button on the form that simple calls the calcManager (Manual mode) ReCalc method. As you can see in the image, it calculates the first total correctly (20.00) but craps out when trying to move to the next calculation. I put a breakpoint on the catch and pasted the following error below...
try
{
ultraCalcManager1.ReCalc(-1);
}
{ }
at Infragistics.Win.UltraWinGrid.RefSummaryValueCollection.RefSummaryValueCollectionEnumerator.MoveNext() at Infragistics.Win.CalcEngine.RangeCalcInfo.EvaluateNextRow() at Infragistics.Win.CalcEngine.UltraCalcEngine.Evaluate(Int64 ticks) at Infragistics.Win.CalcEngine.UltraCalcEngine.Recalc(Int64 ticks, Boolean isStartOfRecalcOperation) at Infragistics.Win.UltraWinCalcManager.UltraCalcManager.ReCalcInternal(Int64 ticks) at Infragistics.Win.UltraWinCalcManager.UltraCalcManager.ReCalc(Int64 millis) at GLExportCS.MainForm.button1_Click(Object sender, EventArgs e) in C:\Documents and Settings\mnewmister\My Documents\Visual Studio 2010\Projects\BOJAppFrameworkShell\GLExportCS\MainForm.cs:line 265
Hi Mike,
Just got the latest version and installed...same problem. However, if I remove the grouping the calculation works fine.
Searched this site and found a couple of other similar posts - one with a case number: CAS-53752-WM7JTL. Has this case been resolved? Ironically, his last post was a day after the latest release dated 17-OCT-2010 so even if it is fixed I doubt it made it into the latest release.
In the meantime, can you please point me to a work around? Maybe point me to a resource that shows me how to perform the calculations with the calcmanager set to "Manual".
Thanks
--mark