Collection was modified; enumeration operation may not execute.

Source     : mscorlib

Stack Trace:
   at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)
   at System.Collections.Generic.List`1.Enumerator.MoveNextRare()
   at System.Collections.Generic.List`1.Enumerator.MoveNext()
   at MicroFour.StrataFrame.UI.Windows.Forms.BaseForm.InitializeFormLoadObjects()
   at MicroFour.StrataFrame.UI.Windows.Forms.BaseForm.OnLoad(EventArgs e)
   at System.Windows.Forms.Form.OnCreateControl()
   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
   at System.Windows.Forms.Control.CreateControl()
   at System.Windows.Forms.Control.WmShowWindow(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WmShowWindow(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativewindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativewindow.WndProc(Message& m)
   at System.Windows.Forms.Nativewindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I have version 1.7.0.0 installed on my desk top machine and the error does not occur there. So - any clue about what vould be causing this?

TIA

Marcia

OK - I know that the problem is occurring because of something that happened when I pointed the app at its database. The question is: how do I wipe out the information that tells the framework which database to connect to and re-point it?

Hi Marcia.

This post might help you:

http://forum.strataframe.net/FindPost18699.aspx

Cheers.

Yeah, Ivan's post should get you going.  Let me know if you are still having issues.  Thanks.

Thanks. I will try that. I knew it had to be something simple.

I tired that. No joy. Any other suggestions?

Well, it looks like a collection is being modified while being enumerated at the same time. What leads you to believe that your connection is causing this problem?

Well, I discovered that it is definitely not the connection. Originally I thought it was because I had issues when pointing the app at the database. However, further investigation shows that the error is occuring in a business object that is being used to populate a datagrid. The exact same code works without error in version 1.7.0.0, but throws an error in version 1.7.0.6.

I have no idea where to start looking. Any ideas?

I will not be able to upgrade my client to the latest version if I can't get this resolved.

Problem solved. It was the loose nut behind the keyboard. I am surprised that this was not a problem in version 1.7.0.0 as well.

LOL...glad you got it figured out!