Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
JozzaTheWick
Starting Member
16 Posts |
 Posted - 2002-09-24 : 13:55:22
|
| All,I want to write a database access layer for the various projects that I will be involved over the next few months. I have seen one that returned the data in Variant arrays, which was easy to code and handled different datatypes well (dates, numbers, text). I want to be able to hide the database access internals (e.g. DAO or ADO) completely - currently our developers are using a mix of both.I know Variants are very memory intensive and (perhaps) slightly slower. However, the current situation has recordset objects everywhere and no error checking or consistency - anything would be an improvement :). We are having problems now as we try to streamline and adapt our applications to be more generic.What have people seen in their own experience? How do people suggest I return data? Currently we do retrieve some large recordsets but I expect this will change as we move more of the logic & calculations off the client and onto the database itself.Cheers,J. |
|
|
royv
Constraint Violating Yak Guru
455 Posts |
Posted - 2002-09-24 : 14:23:00
|
| I suggest you return a delimited string. I have experienced difficulties in trying to return a variant array, especially in web applications.*************************Someone done told you wrong! |
 |
|
|
|
|
|
Using VB variants in my DB access code?