DataGrid BUG? I'm a newbie
-
Hi...I have constructed several Master-Detail forms using the data wizard in vb.net. Most of the time, but not always, a user will be entering data into the datagrid and an extra row appears, like magic, below the row they are working on and it will have a duplicate of the information in the row above it. But the data is not really there! Anyone know what this is ????? Also they have to do an 'update' on each row. Is there anyway for them to be able to enter two rows of data and then do the update? Also I end up with many concurrency errors and foriegn key problems...any advice....Thanks in advance. Thanks, Mike
-
Hi...I have constructed several Master-Detail forms using the data wizard in vb.net. Most of the time, but not always, a user will be entering data into the datagrid and an extra row appears, like magic, below the row they are working on and it will have a duplicate of the information in the row above it. But the data is not really there! Anyone know what this is ????? Also they have to do an 'update' on each row. Is there anyway for them to be able to enter two rows of data and then do the update? Also I end up with many concurrency errors and foriegn key problems...any advice....Thanks in advance. Thanks, Mike
It's hard to tell without any code, but maybe you are having a problem known as "cross product join", where your join condition on the master/detail query is flawed and makes the SQL Server returns multiple combinations of results. As a sample, imagine two tables where they must be joined by the fields A and B. If, in your join condition, you forget to specify one of them, this can lead this kind of problem. Another situation is forgeting to specify a join condition for a table used on a query. I see dumb people
-
It's hard to tell without any code, but maybe you are having a problem known as "cross product join", where your join condition on the master/detail query is flawed and makes the SQL Server returns multiple combinations of results. As a sample, imagine two tables where they must be joined by the fields A and B. If, in your join condition, you forget to specify one of them, this can lead this kind of problem. Another situation is forgeting to specify a join condition for a table used on a query. I see dumb people
Hi Daniel...Thanks for the reply to my post. I can either put the code in a reply or email it to you if you're curious - I ask because it is a couple thousand lines of code generated by the data wizard. If you had a suggestion of what specifically to look for, I could copy and paste it to a reply. On another note, do you know if you can 'update' (uses a merge I believe) more than one row at a time? Again thanks. Mike Thanks, Mike