SQL DataAdapter parameter bindings?

  • Thread starter Thread starter mklapp
  • Start date Start date
M

mklapp

Ok,

I have a SqlDataAdapter (one of 27, there will be
more). Occasionally it loses track of it's parameter
bindings. There are three columns in the Primary Key for
the underlying table.
I have tried reconfiguring the adapter using the
wizard, but the parameter binding screen for existing
procedures (originally created by the same wizard) defies
understanding. I can only select One column and I am not
certain selecting a column on that screen actually does
anything.
This has happened once before. I had to delete
everything associated with the adapter to correct the
situation. This is not acceptable.

1. Any ideas as to what is happening?
2. Why?
3. How do I prevent this from continuing to happen?

tired and frustrated

mklapp
 
And to add isult to injury, rebuilding the objects
results in the deletion of CODE I HAVE ALREADY WRITTEN!
Now I have to write it AGAIN!!!
 
I don't have to write anything again. Sorry for the
rant, long day, too much caffeine and too many 'gotchas'.

However, the original problem is still a problem, but I
may be able to shed light on the situation.

After generating this one particular Adapter, the
underlying query was changed and a Selection parameter
added. The elements retrieved remained the same.

Would this have caused the problem in the original post?

The second post was definitely an IO error (Idiot
Operator).

mklapp
 
mklapp said:
I don't have to write anything again. Sorry for the
rant, long day, too much caffeine and too many 'gotchas'.
Click to expand...

It happens :)
However, the original problem is still a problem, but I
may be able to shed light on the situation.

After generating this one particular Adapter, the
underlying query was changed and a Selection parameter
added. The elements retrieved remained the same.
Click to expand...

I don't understand this. What did you change? Did you change the select
command text?
Would this have caused the problem in the original post?

The second post was definitely an IO error (Idiot
Operator).
Click to expand...

LOL
 
The underlying query is a stored procedure in Sql Server
2000. The original query had only one selection
criteria. I added a second selection parameter directly
to the Stored Procedure using the Enterprise Manager.
This required the DataAdapter be reconfigured.
 
Hi mklapp,

What about delete this data adapter and recreate it?

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
Hi mklapp,

Upon reviewing this thread, I noticed that you already stated that the
solution I offered is unacceptable. I'm sorry about this, but deleting and
recreating the adapter is still my recommendation.

I hope this helps.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
 
Back
Top