I think this question is leading more towards that of "ease of
development" ... keeping the DB open all the time. This obviously
should not be done, and hence my post.
Everyone elses points here are also very valid ...
If I am showing the same data over and over, and that data doesn't
change very often, I build a backend where I can use the database to
store the data, and where I can update it ... but I also have an
"UPDATE WEBSITE" button to recreate the 'static' file on the website
that has the info ... many times, I will have it take my recordset ...
for example ...
values, labels
1234, Option1Name
2345, Option2Name
3456, Option3Name
my backend will take this data, and write a n ASP file with the html
written out for the dropdown box. Then include it in the write spot.
Another example, a products database that only a small handful of
people have access to update, delete, add. I will create each product
it's own formatted static html info in a folder with it's item number
as it's file name, etc...
I want my database open only when completely necessary. But then
again, I am a crazy, performance hungry fiend ... hehe.
Brynn
www.coolpier.com
On Tue, 13 Jan 2004 16:19:16 GMT,
ra*****@online.microsoft.com (Ralph
Hodenius [MS]) wrote:
Hi Graham,
If you are always showing the same data (for example to fill dropdownboxes)
from the database, you can use an application variable to store the
recodset in.
Storing recordsets in session variables is absolute not something you
should do.
Maybe reading article
http://support.microsoft.com/default...b;en-us;258939
Regards,
Ralph
Microsoft
I participate in the group to help give examples of code. I do not guarantee the effects of any code posted. Test all code before use!
Brynn
www.coolpier.com