SqlCommand
-
Hi. Is it possible to read data with the sqlcommand even though the database connection is closed? like: connection.Close(); int returnval = (int)Commandobj.Parameter[something].value;
akkram wrote:
Hi. Is it possible to read data with the sqlcommand even though the database connection is closed?
Why don't you try it and find out? It's the best way to learn.
Deja View - the feeling that you've seen this post before.
-
Hi. Is it possible to read data with the sqlcommand even though the database connection is closed? like: connection.Close(); int returnval = (int)Commandobj.Parameter[something].value;
-
5ed for keeping your cool.:cool:
Deja View - the feeling that you've seen this post before.
-
akkram wrote:
I would if i could, but at the moment im at work and have no way of testing it.
Use Snippet Compiler[^]
#region signature my articles #endregion
-
akkram wrote:
I would if i could, but at the moment im at work and have no way of testing it.
Use Snippet Compiler[^]
#region signature my articles #endregion
-
akkram wrote:
I would if i could, but at the moment im at work and have no way of testing it.
Use Snippet Compiler[^]
#region signature my articles #endregion
Nice. This is a new one for me.
Deja View - the feeling that you've seen this post before.
-
Then I assume that you don't know the answer either and wonder why you even bothered to answer my post. In the mean time ill continue googling for the answer /Thx
akkram wrote:
Then I assume that you don't know the answer either and wonder why you even bothered to answer my post.
No necessarily true: Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime. What the others were trying to to was to teach you that small problems like this are easily testable in a small application. You can then work out the answer from there much faster than posting on a forum and awaiting a response.
akkram wrote:
In the mean time ill continue googling for the answer
And if you try it for yourself you'll have the answer. If you don't have access to visual studio right now then I don't see what advantage you have in knowing the answer right now.
Upcoming FREE developer events: * Glasgow: db4o: An Embeddable Database Engine for Object-Oriented Environments, Mock Objects, SQL Server CLR Integration, Reporting Services ... My website
-
Then I assume that you don't know the answer either and wonder why you even bothered to answer my post. In the mean time ill continue googling for the answer /Thx
akkram wrote:
Then I assume that you don't know the answer either and wonder why you even bothered to answer my post.
That doesn't necessarily follow. If you spend sometime round the boards, you will find that people often post questions before they have tried to find the answer for themselves. Something like this is so simple to prove that it is reasonable to assume that you will have to try it for yourself. The forums aren't here for us to do your work for you, or to do your thinking either. The advice to try it for yourself is good advice. It gets you into the habit of trying things and only coming back once you've run out of things to try or got stuck.
Deja View - the feeling that you've seen this post before.
-
akkram wrote:
Then I assume that you don't know the answer either and wonder why you even bothered to answer my post.
No necessarily true: Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime. What the others were trying to to was to teach you that small problems like this are easily testable in a small application. You can then work out the answer from there much faster than posting on a forum and awaiting a response.
akkram wrote:
In the mean time ill continue googling for the answer
And if you try it for yourself you'll have the answer. If you don't have access to visual studio right now then I don't see what advantage you have in knowing the answer right now.
Upcoming FREE developer events: * Glasgow: db4o: An Embeddable Database Engine for Object-Oriented Environments, Mock Objects, SQL Server CLR Integration, Reporting Services ... My website
Colin Angus Mackay wrote:
And if you try it for yourself you'll have the answer. If you don't have access to visual studio right now then I don't see what advantage you have in knowing the answer right now.
So what you are saying is that there is never an advantage/use to know anything about anything unless when you need to apply that knowledge in practice?
-
Colin Angus Mackay wrote:
And if you try it for yourself you'll have the answer. If you don't have access to visual studio right now then I don't see what advantage you have in knowing the answer right now.
So what you are saying is that there is never an advantage/use to know anything about anything unless when you need to apply that knowledge in practice?
akkram wrote:
So what you are saying is that there is never an advantage/use to know anything about anything unless when you need to apply that knowledge in practice?
No, I'm saying that the urgency in which you seem to be attempting to gain this current piece of information isn't immediately necessary.
Upcoming FREE developer events: * Glasgow: db4o: An Embeddable Database Engine for Object-Oriented Environments, Mock Objects, SQL Server CLR Integration, Reporting Services ... My website
-
Then I assume that you don't know the answer either and wonder why you even bothered to answer my post. In the mean time ill continue googling for the answer /Thx
-
Nice. This is a new one for me.
Deja View - the feeling that you've seen this post before.
-
You can't really blame this guy for not wanting to try anything out for himself, it's an extremely easy route to try in life. I blame it on the parents.
althamda wrote:
I blame it on the parents.
You think they should have exercised some self-restraint?
Deja View - the feeling that you've seen this post before.
-
Oh, Mac, there's your problem.
-
Colin Angus Mackay wrote:
And if you try it for yourself you'll have the answer. If you don't have access to visual studio right now then I don't see what advantage you have in knowing the answer right now.
So what you are saying is that there is never an advantage/use to know anything about anything unless when you need to apply that knowledge in practice?
No, what they're all saying is that if you don't have the skillset to wip up a small test app and test whether this is possible or not and do the research yourself, your career as a developer is over before it even begins. Being able to do your own research, learn new technologies, testing your hypothesis, ..., are essential skills to surviving in the world of software development.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Hi. Is it possible to read data with the sqlcommand even though the database connection is closed? like: connection.Close(); int returnval = (int)Commandobj.Parameter[something].value;
One of the greatest things about "software engineering" is that you can try out all sorts of strange things and no matter how bad the result is, you're unlikely to do any real damage to anything. Never be afraid to just try; we learn more from our mistakes than from getting it right the first time.