-
I have a project that uses about a dozen ADODC's on one form. In the interest of conserving memory (running the app currently sucks up about 12-13 megs RAM), I've been deliberating whether converting some of these Data Controls into code will make much of a difference.
One problem is I use a _lot_ of DataGrids, and they simply won't accept a code recordset (I have tried extensively with "set DataGrid.DataSource = rs, and it doesn't have an effect").
I've also linked up a _ton_ of textboxes to various Data Controls, and writing up all these links in code using the .DataSource property is going to be a chore. So the question is, will it be worth all the trouble changing to code, or will it not really make much of a difference? If there is a difference, what kind of performance increase can I expect?
-
Have you ever thought of using the dataenvironment? Check it out. Its a great help for programmers.
Its more like of the .rs but you could bind it to all controls possible just like adodc.
Hope this helps.
-
i agree with rives..data environment really helps. and once you get the hang of it you'll probably like it more that adodc's. if you want to know more, vbpj's got an online article on it.
go to http://www.vbpj.com and register (you need to in order to see the article), then click on Locator+ and type VBPJ0799 into the box. this includes all code listing plus the code project files.
