Lesson 5, How do you write an application without using any of your own
code.
A. Ask questions on forums like this and let others do the coding for
you, at the end, you will have learned a lot about asking questions and
nothing about developing your own ideas of how to solve a programming
problem.
Loading
theLizardPosted Mar 2, 2010, 2:44 AM
No Sam, I have never indicated that my way was the only way only that it was a simpler way, there is a difference and I am not misinforming others here.
Explain to those on this forum that do not understand what it means, in detail, what deprecation is.
Wait here it is in wiki
In computer software or authoring programs standards and documentation, the term deprecation is applied to software features that are superseded and should be avoided. Although deprecated features remain in the current version, their use may raise warning messages recommending alternate practices, and deprecation may indicate that the feature will be removed in the future. Features are deprecated—rather than being removed—in order to provide backward compatibility and give programmers who have used the feature time to bring their code into compliance with the new standard.
Nowhere does it state that the whole will be removed.
There are mountains of examples of deprecated functions in windows but you can still use them albeit not advised.
functionX(int y) is depracated by functionXA(long int y)
I mean even some 16 bit windows applications will run on Vista,they use functions long considered extinct in 32bit windows same will be the case in 64bit and 128bit and 256bit etc. etc.
Sam HobbsPosted Mar 2, 2010, 12:52 AM
You are misinforming people by ignoring the truth that Microsoft has stated an intent to deprecate ODBC.
Mahesh ChandPosted Mar 1, 2010, 11:35 PM
We will monitor forums and work on your suggestion. I do agree we should not answer a question unless we know the answer. This is why we have rating and thumbs up and thumbs down options on the forums ;).
theLizardPosted Mar 1, 2010, 11:28 PM
Again I agree with you, but telling some one to plant crops in the desert without water does not produce food, so giving the wrong information does not produce a programmer sometimes it is best NOT to answer questions if you do not now the answer.
To put this another way, if some one asks where can I grow food?
An answer comes back, the desert, (this is ok you can grow food in the desert)
Then the question comes back, but what about water?
Answer comes back, Squeeze it from rocks.
Now clearly this is wrong information, do you allow this information to be accepted or do you correct it?
In regards to ODBC and your reply, yes I know but it is not me that you need to convince, but I do need to correct you on one thing, ODBC is for Microsoft Databases as well as "Non" Microsoft databases and it will be around for a very long time.
I am not trying to be a smart A... but people here want to learn and some of the answers I see don't help at all, I am NOT an expert, I do not pretend to be and there are question I cannot answer or attempt to answer because I am not qualified enough in the area of the question to answer, but there are those who try to for the sake of earning extra points (I do not begrudge people from earning a little extra cash) who should not even attempt to answer because it is clearly not their area of expertise.
If you or others want to disagree with this that is ok but this is my belief.
Mahesh ChandPosted Mar 1, 2010, 10:30 PM
That said, the purpose of forums is simple. Share information. If somebody is helping others, I don't think you or I should have any problem with it. I have seen on this site, people learned from my articles and once they start writing applications, they start sharing with others. Same applies to forums. Back in the day, it was just me. Then more people joined and people who learned from the site, they start helping others.
It's simple.
Now, if you take an example and say, giving food to poor countries is not going to help. Just tell them how to work and earn the food. But before that, they have to be fed. Then they will be able to work.
Agree?
C# Corner is a community website and we are open to all ideas that help users. We vote and which idea we see fits, we implement it. If you have any ideas or suggestions that would help users, please do not hesitate to share with us.
Now back to ODBC. ODBC support is there and will be there to connect and work with non Microsoft databases.
Hope I answered your question.
theLizardPosted Mar 1, 2010, 3:45 PM
Then you start suggesting things you obviously know little about, have you ever used ODBC outside your comfort zone, have you used ODBC without using DataTables, or data bound component for that matter, I think NOT Sam.
Lets say you had a need to open an oracle db and an mssq db and a postgress db from the same application what would you use to do that with?
Microsoft depractes a LOT of things but that does NOT mean that ODBC is dead.
Stop your rubbish, this is a forum to HELP people and you are not helping by putting out wrong information.
Sam HobbsPosted Mar 1, 2010, 2:00 PM
If someone posts an incorrect suggestion, then you should post the correct answer. Don't criticize someone else's answer without providing the correct information. For example, 64-bit Windows is shipped without 64-bit drivers for ODBC. Instead of criticizing me for saying that Microsoft is dropping support of ODBC, provide an answer to the question of how to use ODBC in a 64-bit application. If you had researched that, you would have learned that what I said is accurate.
Can you admit that Microsoft has stated the intent to deprecate ODBC?
theLizardPosted Mar 1, 2010, 4:54 AM
Some people actually give up their time to answer questions on forums like this for no reward whatsoever.
beginners teaching beginners does NOT produce teachers..
Sam HobbsPosted Mar 1, 2010, 4:30 AM