No problem.

Ben,

That fixed the problem  Thanks for the quick response.

-Larry

I have it fixed, Larry, and I should have the update available around the time that you get into the office (in a couple of hours).

Ben,

Any estimate of when a fix will be available? If it's going to be awhile I'll go back to v1.4

-Larry

I think I figured it out, Larry, the ListChanged event is being fired too soon (before the record has actually been initialized).  I'm working on a fix right now.

Ben,

A red error window is never displayed. Attached is a screen shot with the stack trace associated with the error.

-Larry

When it gives you that error for each field, do you get the red error window?  I'm wondering if the stack trace within that error window contains a call to "CurrencyManager.ListChanged" or "CurrencyManager.OnListChanged."  .NET might be trying to do something when the internal DataTable changes rather than waiting for the row to be initialized.

Ben,

It took me a few minutes to get back to you since I had to re-install v1.41.

Continuing just brings up the same error for the next field and so on. Once I've cycled through all the fields the maint form is displayed and I'm able to enter the data and save the record.

-Larry

Hehe, I was just replying Larry  

When you get the exception in your program, and the .NET unhandled exception dialog pops up, press "Continue" on your debug and you should get the red "Application Error" window that will have a complete list of the exceptions and inner exceptions and the stack traces of all of the exceptions concatenated together.  That should give me a clue where it's coming from.  You can copy/paste the content of that window and post it here.

Ben,

Whatever is causing the problem appears to have been introduced in v1.41. I moved the code back to version 1.4 and everything works as expected.

-Larry