Has anyone else encountered problems while trying to add a new record using ado.net while working in VB.NET? I am seriously beginning to wonder if there is a bug in the software. For instance:
I have my application working, tested and can add, delete, save and cancel records using data adapters and datasets with bound controls. However, as soon as I try ANYTHING else, such as only adding a new control to the form, my whole app breaks! I haven't even added any new code, just strictly dragged a control on it, and the add new record will not work anymore. And it doesn't have to be just adding a control, it's broke on me when I did try to add code for a different button, or anything that would be outside of the "addbutton_click" routine. I have spent 2 months trying to get this add record feature to work, and finallly solved it, but now find out it won't stay working. At first I thought it was my skill level, that I was doing something wrong, but the same exact scenario has happened to 2 other programmers, who were trying it on 2 different pc's. They got the same result. Sometimes it works, sometimes it won't. I fixed it this last time by retyping each line of code in the add button routine, then deleting the old. It worked! Just to make sure I ran it a 2nd time, I did not do anything else besides hit run a 2nd time, and it broke! It would not add a record, even though just 2 secs before it worked and my new record was being displayed!
I should mention that I use the wizard to do all the configuring of the data adapter and dataset. Which brings me to ask if anyone has encountered problems while using that as well? I can make a new connection, redo the adapters, dataset, and it will still point to an old table that is no longer on my pc. It seems like the wizard cannot let go of something in memory. I solved that problem by shutting down my pc and rebooting and then the wizard deleted my old settings. This is a serious problem in my opinion. So everytime I need to reconfigure I have to shut down?
I am no longer so keen on using VB.NET and am ready to give up using it because of these glitches in the software. I would welcome anyone else's experiences using VS 2003 and if you've had problems as well????