delete command keeps disappearing on the datadapter

[Ralf]

I have an oracle data adapter built. I did it thru vb.net controls.
The query used access' multiple tables, so the delete and update
commands will not get built. This has not been a problem in the past,
I just go in the adapter properties and create the command there. So,
when I use it in code, I can chage the commandtext to what I need to
delete. Well, now I am trying that with another adapter and it keeps
disappearing. After compile, it is still there. But, after starting
the app in DEBUG, it is gone right away. What seems to be the problem
with it?

 

[Ralf]

Here is more info that adds to the strangeness. I went and created a
new dataadapter and configured it with the exact same select statement.
I can now add the 'update' and 'delete' commands after the fact and
they stay there. In the previous adapter, it would create but would
disappear as soon as I started the app. Now, the new problem is with
the delete statement. The connection command for delete goes away. I
created one for both the 'update' and the 'delete', the one from the
update stuck but the one from the delete keeps disappearing.

This functionality was working great and has been for 2 weeks. Now, I
have done something that has hosed it up greatly, and I haven't been
working in this module either, and I am concerned that .NET is not
being reliable enough for the application I am building

 

[Ralf]

Once again, another strange thing happening with .NET. I have been
creating, deleting, and trying this over and over again with the
adapter and dataset to get it to work. A common problem I have run
into with the dataset is enforcing constraints. This is b/c I am doing
joins and I don't want to enforce them. So, I have been changing this
to 'false' all thru my app. Now, with the problems I have been having,
I should have expected something wacky to happen. I change the
property to false, compile, and check the properties of the dataset to
ensure it stayed changed. It did. So, I start the app in debug mode,
and then look at the properties again to ensure it is still 'false'.
It has changed back to 'true' for some reason!!!

What could be my issue here? I have no idea and have been fighting
this thing for 1.5 days with no luck, just more things keep popping up
that is wrong. I am looking for any kind of ideas anyone might have.
My company automatically pushes updates to my machine, so I am going to
look into maybe an update has hosed this, but I'm not betting on that.