Ok, you probably should setup some global function to get that connection stuff.
and use a datatable in place of a dataset (a dataset is a collection of tables - you only have and need one)..
But, you can do this:
Session["MyAccess"] = access;
Now, on any other web page, you can do this:
Datatable access = Session["MyAccess']
At this point then, any value in that table can be had like this:
string strTest = access.Rows[0]["some column name here]"
So, once you shove the table into session[], then you can pull that table out back into a datatable anytime you want from that point on - it will persist for life time of that logged on user session.
Note that I have in some cases pulled out a row, and thus don't even have to use the rows collection, since you (we assume) ever only have one row. However, for some strange reason, a data row cannot be serialized, and if you use sql server (or I suppose oracle) based session management, then it uses serialization.
But, no worries a dataset, (or better datatable) can be serialized , and thus you should have no issues shoving (saving) that table into session.
Regards,
Albert D. Kallal (Access MVP 2003-2017)
Edmonton, Alberta Canada