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,
What version of the controls are you using? If you do not already have it, I recommend that you get the latest Service Release.
How to get the latest service release - Infragistics Community
If that does not help, we will need to be able to duplicate the exception so we can get it corrected. Can you post a small sample project here so we can check it out?
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
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?
>>Did you get the service release?
Originally no, not until you just now clarified what I needed. I had gotten only the product release.
I just now installed the service release but it did not help.
Okay.. if the service release did not help, then the issue you are encountering must not be the same issue that was fixed. In which case, we are back to square one - we need to be able to reproduce the issue here so we can get it fixed.
Are you able to duplicate the exception in a small sample project and post it here so we can check it out?
How do I do that?
I tried adding the attachment as a reply to this post but i said it was too big - even though it's zipped.
I was able to make it smaller...
Hello,
I have submitted a developement issue related to the issue with the CalcManager. The reference ID is 66976. I will provide more details through a support case.
Mark,
You can make sure that the assemblies are included in the click once deployment by setting the Publish Status on the Application Files dialog. To do this with VS2010, follow these steps:
This should correct the behavior that you are seeing.
One possible cause of the change in behavior that you have seen is if the Copy Local value of the Reference(s) changed as this determines whether the references are included or are a prerequisite when the default of (Auto) is used.
You can refer to the How to: Specify Which Files Are Published by ClickOnce topic on MSDN for more details on how to specify what gets published.
Let me know if you have any questions with this matter.
Hey Mike,
On a side note...
For this application, and up to this point, I have been simply publishing my app to a network share so I can easily install and upgrade (via clickonce) users machines.
Now, after I loading the latest release and service release and running the upgrade utility on my project, when users are prompted to upgrade (again, via clickonce dialog) the app is saying that the infragistics controls need to be installed in the GAC - which I never had to do before - at least manually/personally myself.
My app is a full trust ClickOnce app with no signing.
Do you have any suggestions?
thanks
Your right, changing the name for the band key keeps it from crashing. However, if I don't change the name and, if you remove the summary in question (drsum - crsum), the other two summarys still work fine. But then again, it doesn't need/use the calc manager to perform those simple sum calcs.
I took a quick look just to see if there is something unusual in your code that is causing this and I think I see a problem.
The exception I am getting is that the CalcManager is failing to find a grid band named "GLTable."
When you set up your data structure for the grid at design-time, you set the key of the root band (the only band) to "GLTable".
But the data source you are binding to is not using that name. The DataSet you are getting here has only one table and the TableName is set to "Table" (without the "GL").
If you go into the grid designer and change the Key of the root band to "Table" the exception goes away. There still seems to be a problem here, because the summary is returning a reference error. But at least it's not blowing up and the mismatch of the table names is definitely a problem.