StrataFrame Forum

Error when using grid

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

By Michael Reese - 10/15/2006

I am using a standard grid and calling the SF Standard form. I am able to update the CustomersBO object from the Grid. However, when I exit the form containing the grid and reload, I get the message below.

ArgumentException
 Key already exists
Parameter name: Key

Components

GridView

CustomersBO

BusinessBindingsource

Childformdiaglog calling a standard SFform

Michael

By StrataFrame Team - 10/16/2006

I'll see if I can reproduce it...
By Michael Reese - 10/16/2006

Thanks Ben

Thanks, I need to further explain that my windows gridview is one form (When loading the grid, I am using customersbo1.filltop100. Wink  and I am performing the add.update,delete on a second form.  When updating, i am using customersBO1.edit and using CustomersBO1.SeekToPrimaryKey(PrimaryKeyValue).

All works fine until I reload the form with the gridview.

Michael

By StrataFrame Team - 10/16/2006

When you reload the form with the gridview, are you just requerying the data, or are you just opening the child form again?
By Michael Reese - 10/16/2006

I tried requery after updaing the the bo. Then used the standard fillby100 first in the BO parentformloading then in the initialize.
By Michael Reese - 10/21/2006

Hello Trent

I am having the same issue with the Ultragrid

By Trent L. Taylor - 10/21/2006

We will take a look at this on Monday and see if we can reproduce the behavior.
By Ivan George Borges - 10/23/2006

Hi Trent.

Just to add something ... I tried the UltraGrid. I added a new row, typed the data and went for "Save". The application hanged with no message.

By Trent L. Taylor - 10/23/2006

Yes, there was an issue when using the BusinessBindingSource...which I assume you are using.  This has been fixed...just download the latest build from the My Account area of the site and try again and see if the error persists. Smile  Thanks.
By Ivan George Borges - 10/23/2006

I will try only thinking about the problem and come to the forum to see if you have already fixed it ... w00t
By Trent L. Taylor - 10/23/2006

hehe...I make no promises Smile
By Paul Chase - 10/23/2006

Trent,

This updated release does not appear to be available on my account. The latest release I have on my account is from the 9th although I did go through downloading / uninstalling /reinstalling on the off chance that the download was the updated one you spoke of. I hope it wasn't the updated version because it still hangs on save for me Smile.

I am guessing that you are passing out interim builds to whoever is having the problem?

Also would it be to much trouble to have a "Known Issues" section of the forum for things like this? You as a moderator could move a thread like this into that section until a build is generally released and available. Something along those lines would be nice as it would have saved me a bit of time tonight.

Thanks

Pail  

By Trent L. Taylor - 10/24/2006

Paul,

We are looking into this to make sure there is not a scenario that we missed.  I wil let you know more once we do some more testing.  Thanks.

By Paul Chase - 10/24/2006

Thanks Trent,

No problem I am not in a great hurry trust me I have plenty of other things to keep me busy! It was just confusing in that it sounded like a build was available for download to address this issue and in reality it was not there. It was just a bit frustrating after experiencing the issue trying different things to find out what was causing it (I wasnt sure it was Strataframe) then finally finding this thread and thinking that the fix was available and I that could continue and finish the work i was doing.

I was just suggesting that it would be nice to be able to more easily identify the known issues with the current release and whether or not there is an interim build or workaround for it. Anyways I think you guys are doing a bang up job and am just offering this as a suggestion to help.

Paul

By Trent L. Taylor - 10/24/2006

I understand...the confusing part is that there are apparently two separate saving issues.  Once which we have fixed (and even though the date indicates the 9th, it was posted later than that...we'll correct that the next go around).  So that is why I thought that you were running into the same issue.  I may query you for more details later, but for now I think we have the scenario we need.  Thanks for your input.