Relearning old ASP/ODBC tricks

ben.kimball

Can someone show me the "new way" to do the following (old ASP/ADO code shown) with ASP.NET/ADO.NET? This was opening a table and adding a new row without using any actual SQL SELECT/UPDATE statements. Thanks! <% 'Get data from Request object SendTo = Request.Form("PID") Message = Request.Form("Message") 'Open database connection Set dbConn = Server.CreateObject("ADODB.Connection") dbConn.Open "DSN=dataBaseName;uid=someUid;pwd=xxxx" 'Attach to XMessage table in database Set rsXMessage = CreateObject("ADODB.Recordset") rsXMessage.Open "XMessages", dbConn, adOpenKeySet, adLockOptimistic 'Add new row to table rsXMessage.AddNew 'Set row data rsXMessage("XTo") = SendTo rsXMessage("XFromID") = Session("ID") rsXMessage("XFromName") = Session("Name") rsXMessage("SentWhen") = Now rsXMessage("Message") = Message 'Commit/Update changes to row data rsXMessage.Update 'Close database connection rsXMessage.Close %>

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

ben.kimball22y ago
Ugh! Yes, what you say makes a lot of sense. It will be more efficient, just not as much fun to code. (And the code isn't as "pretty") :( I guess I have a lot of old habits to unlearn. :) I did find a way, somewhat, to do the column name resolution, just ugly and quite a pain. And pretty slow, bet it's the overhead you were talking about. I'd better just get away from it: dtTerrainImages.Rows[Terrain]["image"].ToString(); becomes stTerrainImages.Rows[22][2].ToString(); Ugly! :) Thanks!
+1
sjones22y ago
You don't get all the help old ADO used to give you in setting up a Recordset. In the background there was a lot of back and forth asking for column names, data types, contraints, etc. As you can imagine there is a lot of overhead in doing that. Mr. Helpful in Redmond decided we didn't need that anymore. Now you're on your own. If you create the database, you should know what it looks like. No point wasting all this time getting info you already know but are too lazy to type in yourself. I say that sarcastically because I can see both sides of the argument. There are ways for you to still get this done the way you want to. You need to look at the DataAdapter. If you are just learning ADO.NET, better clear your calendar. This will take a while to get used to. The idea is to force us to be more efficient. In the example you give, the overhead of creating a recordset is truely a waste. All you need to do is insert a record, so just use a simple INSERT INTO sql statement. Much quicker, much easier to code, and much more efficient.
+1