TableAdapter not Refreshing on configure

[bblanco]

I've had trouble with project DataSet objects created by VS.Net. If I go into
my database and change my table structure or modify my Select store procedure
the TableAdaptor does not make the adjustments. I read that "Configure" is
supposed to refresh the TableAdpater after VS2005 SP1. I've tried VS2005 SP1
and VS2008. I "configure" the tabledadapter and it does not help. If I do to
DataSet1.xsd and right-click on my TableAdapter and click PreviewData, I see
the adjusted datastructure in the query result. But, If I go and create a new
ObjectDataSource and gridview. The changes that I have made do not appear.
The ObjectDataSource still only sees the original structure and parameters.
I have found the only way for the TableAdaptor or its resulting DataSources
to reflex any changes I make to my data structure or stored procedures is if
I completely delete the DataTable from the Dataset and recreate it.

So, what am I missing why is the dataset not being refreshed or
reconfigured? Is there a chache I need to clear?

 

[Cor Ligthert[MVP]]

bblanco,

Are you sure that you don't have created and extra st dataset.
It is impossible that the grid can have the same datasource as that is not
anymore in your code.

Cor

 

[bblanco]

Cor,

I don't understand your post. Will you please clearify?

bblanco

 

[Cor Ligthert[MVP]]

Did you search your code including the hidden part if that old dataset does
not sustain.

Especially in version 2003 this was often a reason for problems.
(I know you are using 2005 and 2008)

Cor

 

[bblanco]

I should not have to search. Microsoft claims that he "Configure" function
should refresh the TableAdapter. It would just be easier to delete and
recreate the TableAdapter than search through code and manually make changes
everythime I make a change.

 

[Cor Ligthert[MVP]]

I should not have to search. Microsoft claims that he "Configure" function

should refresh the TableAdapter.

The sun shines forever in Florida, that does not mean that there cannot be
sometimes clouds before that.

Cor

 

[Frank Hauptlorenz]

Hi bblanco,

I've the same issue with VS2008 sometimes. Try to configure the button a
second time and remove the square brackets
and finish the dialog. This helps for me.

Frank

 

[bblanco]

Cor,

What in the world does the weather in Florida have to do with configure
option appearently not working in VS.Net??

Are you saying that there is no resolution to this failing configure option?

Are you saying the only way to refresh the TableAdapter is to manually
change the code? It would be more expediant to write the whole dataset
myself, or delete the tableadapter and recreate it. But that is not they way
it is supposed to work.

Has Microsoft just been ignoring this issue for years? This issue was there
for VS2005 and remains for VS2008. They claim it was fixed with VS2005 SP1.
It's not, unless there is something I'm missing. What am I missing?

But yours response is in essence: "Live with it."?

We've paid a heck of a lot of maoney for these products. I expect better!

 

[bblanco]

Frank,

Thanks for your resonse, but could you please clearify? Where are these
brackets that I need to remove?

Ben

 

[Cor Ligthert[MVP]]

We've paid a heck of a lot of maoney for these products. I expect better!

If you know that it is a real bug then you can contact your Microsoft
office.

I don't know if that is still, but in past as you "really" proofed that it
was a bug and that was accepted, then the assistance was free.

Beside that I thought that every MSDN subscribtion you have, gives two times
free assistance when needed.

While as you vistit these newsgroups with your MSDN password using the MSDN
newsgroup webbrowser, for sure an MSFT will give you a reply as he is not
absolute sure your question is answered.

Cor

 

[Frank Hauptlorenz]

They are in the generated SQL of the tableadapter. Like this:

SELECT X,Y,A FROM Z WHERE [X]=@Original_X

as an example. Remove the bracket from the X (and the others). This is
working for me, updating the TA in VS2008 correctly.
Seems to me to be a bug.

Frank