O
Oriane
Hi,
I write a classic windows form application in ado .NET, with 4 grids. There are only child-parent relations in a unique dataset containing 4 tables : client->site->command->product. I mean a command is composed of products, a site has many commands...
I wrote event-handlers attached to the dataset so that when a row is selected in a particular grid (whose datasource is the dataset), a function called by the event-handler is in charge of refreshing the other datagrids.
It works correctly for a while, and suddenly the behaviour is no more correct and the datagrids are not refreshed.
When I look inside with the debugger in VStudio .NET I can see that the callback function is entered, but when I click on "NEXT" to jump to the first executable intruction, I quit VStudio and go back to the application.
I can't explain this behaviour...
Any idea ?
Oriane
I write a classic windows form application in ado .NET, with 4 grids. There are only child-parent relations in a unique dataset containing 4 tables : client->site->command->product. I mean a command is composed of products, a site has many commands...
I wrote event-handlers attached to the dataset so that when a row is selected in a particular grid (whose datasource is the dataset), a function called by the event-handler is in charge of refreshing the other datagrids.
It works correctly for a while, and suddenly the behaviour is no more correct and the datagrids are not refreshed.
When I look inside with the debugger in VStudio .NET I can see that the callback function is entered, but when I click on "NEXT" to jump to the first executable intruction, I quit VStudio and go back to the application.
I can't explain this behaviour...
Any idea ?
Oriane