I have the most basic setup imagineable: A form with a bunch of textboxes connected through MS's binding source to your dataset (as opposed to MS dataset). For the most part, it works OK. But every time I make a change to the table adaptors in your dataset, it completely disappears from the form's view. The dataset still exists, but the form doesn't recognize it anymore. It acts exactly as if I actually deleted the dataset, but of course I did not. I have to delete and then completely rebuild the dataset each time this happens.
This has happened 5 times now and frankly, I don't have time to keep recreating datasets. I can change an MS dataset all day long with no problem.
So, what is up with this...?
What Causes Your MySQLDirect.net Dataset to Disappear
-
- Posts: 4
- Joined: Sun 03 Jun 2007 01:57
-
- Posts: 4
- Joined: Sun 03 Jun 2007 01:57
I modify the dataset using designer and I call the wizard from the menu. The form was open at the time of dataset edits. I would then either get the hated screen of death going back into the form designer or get errors on a build. Once I remove references to the dataset, the build will go.
The changes to the dataset usually involve adding queries to a table adapter.
I am using v 4.0.9.0 pro with VS2005
The changes to the dataset usually involve adding queries to a table adapter.
I am using v 4.0.9.0 pro with VS2005