Hello,

I am beating my brain trying to figure out what I did wrong. I am using an infragistics grid. I am setting the isListSource property to true in the BO and binding the BO to the grid.

In the AfterRowUpdate event of the grid, I am calling BO.Save();

This works fine on another form. Records are added, deleted and modified just peachy, but on this one form, the save method gives me this error:

"The CurrentRow could not be evaluated because the CurrentRowIndex is out of range.  Business object record count: 1.  CurrentRowIndex: -1."

Does this error give you any clues as what I'm missing?

Thanks!

You're not clogging anything.  That is what the forum is for.  If you start running into a problem again let me know.  I know that the Infragistics grid can be finicky at times when interacting with an ADO.NET data table.

hi,



found this thread and i'm also having problems with save. I'm trying to add a new record everything seems to work ok, when i click new i get an empty form with a ID of -1 but when i click save nothing happens the form just hang with no error given. i thought i was doing something wrong so i tried the same step in the sample project and same thing. no error the form just hangs. Have you ever experienced something like this?

No.  But the first thing that you need to do is place the application in debug mode and see what is being executed on the server.  To do this you need to set the debug mode and file in the AppMain of the project.  It will look like this:

MicroFour.StrataFrame.Data.DataBasics.DataSources(0).SetDebugOn("c:\temp\mydebugfile.html", True)

Place the above code right after the ConnectionManager.SetConnections() in the SetDataSources() method in AppMain.  This will create an HTML file with every SELECT, INSERT, UPDATE, and DELETE call made through the framework during the session.  The file is updated before it is actually executed on the server, so even if it hangs, it should show up in the file.

The next question is what type of database are you using when this happens (also include what version)?  Run the app in debug mode first and see if it clues you in to what is going on then we can go from there.