What is "so superior" about asking your for you complete code and letting
you know why it was asked for?

Geeze, take the chip off your shoulder! If you admit you are so
inexperienced, then perhaps you could have just responded to my second reply
with "oh, I didn't realize that if I just told you the connection string was
ok, that this wouldn't be enough to diagnose the problem."

The person who has the attitude here is you! I was trying to help you
(until you brought your "just give me the answer and I don't need to answer
your questions" attittude to the table).

[quoted text, click to view]

Scotts right, even though you use a connection in one place and it works
fine there, that doesn't mean it will work right in all situations. I've
seen people accidentally use connections they have for a sql connection then
try to pass that to an oledb connection so that's why it's important. We've
also helped people that had connection string problems simply because they
used the wrong connection string name or spelling in their code and they
swore up and down that the connection string and the call to get it were
correct. Technically they were right, just misspelled their connection
string and it happens to the best of us which is why we ask.

Does the page run without any errors at all? Have you checked to see that
data is being returned? One think I often do with a dataset is use the
Trace.Write() method to output information about the dataset to the trace
file. Things like how many tables, the names of the tables and the number of
rows of each. If you can get this far then you can definitely see that data
is getting passed and know for sure that data retrieval works. When
something like this isn't working, the first thing I always try is dump some
message using Trace.Write just as soon as the event starts so I'm sure the
event is actually firing. Sometimes the event doesn't fire and it's easy to
end up running down a rathole looking for the wrong error.


--
Hope this helps,
Mark Fitzpatrick
Microsoft MVP - Expression

[quoted text, click to view]

Thanks Mark, I have actually solved my issue, it was along the lines
you mentioned, I was not actually getting anything in my DataSet.

I intend to experiment with the Trace command as I have no knoweldge
oir experience with this. It should prove very helpful as you say for
testing purposes.

Can I ask another question here.....

How do I write text into the footer of my dataView?

I have tried all sorts of variations on all sorts of things and
obviously I have not hit on the right combination of objects.

INitially I would like to be able to do something simple like:

GridView.FooterRow.Text = "Test message" (I know that does not work!)

But later I would like to have the text come from another Datatable in
my dataset.

Any assistance would be appreciated.

If I should postz this as a new thread please let me know.

Hi,
What's is the error your're getting?