a collect

Posts   
 
    
vanaeken
User
Posts: 6
Joined: 09-Dec-2004
# Posted on: 27-May-2005 09:50:32   

We derive a class from a LLBLGen collection (self-servicing). When databinding an object of this class to a DataGrid and deleting the last row through the GUI, we get the following exception: error when commiting the row to the original datastore - specified argument was out of the range of valid values - parameter name 'index' was out of range.

Any ideas what's wrong? We do not have this issue with collections not derived from a LLBLGen collection.

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39933
Joined: 17-Aug-2003
# Posted on: 27-May-2005 10:01:49   

Which grid are you using? Which version of llblgen pro are you using? (i.e. latest version, or an older version?) Silly question: does it occur always or just with the last row?

Also, do you refresh the grid when an event is fired from the collection?

Frans Bouma | Lead developer LLBLGen Pro
vanaeken
User
Posts: 6
Joined: 09-Dec-2004
# Posted on: 27-May-2005 10:31:14   

The LLBLGen version we are using is 1.0.2004.1. We get the exception only when deleting the last row. We do not handle any events since we assume that the collection takes care of refreshing the grid. Is this assumption incorrect?

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39933
Joined: 17-Aug-2003
# Posted on: 27-May-2005 11:17:32   

vanaeken wrote:

The LLBLGen version we are using is 1.0.2004.1. We get the exception only when deleting the last row. We do not handle any events since we assume that the collection takes care of refreshing the grid. Is this assumption incorrect?

It should, but there were some issues with older versions of 1.0.2004.1 and ListChanged. The last version of 1.0.2004.1 runtimes are available on the website still, in the runtime libraries section.

I'll see if I can reproduce it here with 1.0.2004.2.

Frans Bouma | Lead developer LLBLGen Pro
vanaeken
User
Posts: 6
Joined: 09-Dec-2004
# Posted on: 27-May-2005 11:49:36   

The latest runtime of 1.0.2004.1 does not solve the problem, but the latest version of LLBLGen (which we just downloaded) does. Great!

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39933
Joined: 17-Aug-2003
# Posted on: 27-May-2005 12:10:50   

vanaeken wrote:

The latest runtime of 1.0.2004.1 does not solve the problem, but the latest version of LLBLGen (which we just downloaded) does. Great!

Ok! simple_smile

Yes it's something with the order in which the events are fired. Glad it's solved! simple_smile

Frans Bouma | Lead developer LLBLGen Pro