Josue Given all of the information you put in the post above the first and most obvious answer is that there is no data in the database. Now, your next post will say that there is indeed data in the database. then someone will ask you to post the statement you are executing and the code you use to process it. Then you post it and then someone will look at it and answer it... Let's skip the next few steps and you post all of the info about the problem you can, processing code, the SQL statement, and anything else you think is pertinent. sorry if this came off as rude, but you didn't tell us anyhting, so how can we answer a question...
Joined: Feb 06, 2001
I can understand your response. It really wasn't a lot to go on, but I do appreciate the summary. And I especially appreciate you taking time to respond. I was able to solve the problem. I was assuming that it was a problem with the driver (and it still may be). I was testing a "null" result in the stored procedure and the result was not understood. So I changed the test and it worked. Thanks again.