Asp.net caching vs Access Caching.

[olle]

Hi folks.
I learning asp.net and compare it with traditional asp and
Access-developing.

The issue is this one:
1/I have this Ms Acceess adp-project application that works fine on my
Ms Sql server database.
In my main form I have an Access-combobox with Customer-names from my
customer table.
In this combo-box are about 2000 records.
With this combobox the users can make a database query to work on only
the records in
my main table that are related to the customer they have chosen.
In this situation the comboxbox load very quickly.

2/ Then I moved the sql server databases to a remote server.
Then I connect though my Client Access2000-adp file through internet.
Now the combobox with customer names loads more slowly, but only then
first time when I load the Access main-form.
Then it seems that the combobox is cached somehow because then the
users can look for customer-records fast and convient.
Also this approch is OK for my users.

3/ And now I try the same approach with an asp.net-webform.
I cach the datsource for the asp.net dropdown. But even so, in this
case the customers asp:dropdown loads slowly on every postback I make.
I think now that my users used to my userfriendly Access-forms wouln't
like the move from the Access app. into an asp.net app.

Thinking about if there is a possibilty to cach comboboxes and
dropdowns on the client the way Access-projekt-asp-forms can do with
Visual studio dot net.
Does anyone know about these issues?
BigOlle

[Bob Alston]

ol**@ylm.se wrote:

Hi folks.
I learning asp.net and compare it with traditional asp and
Access-developing.

The issue is this one:
1/I have this Ms Acceess adp-project application that works fine on my
Ms Sql server database.
In my main form I have an Access-combobox with Customer-names from my
customer table.
In this combo-box are about 2000 records.
With this combobox the users can make a database query to work on only
the records in
my main table that are related to the customer they have chosen.
In this situation the comboxbox load very quickly.

2/ Then I moved the sql server databases to a remote server.
Then I connect though my Client Access2000-adp file through internet.
Now the combobox with customer names loads more slowly, but only then
first time when I load the Access main-form.
Then it seems that the combobox is cached somehow because then the
users can look for customer-records fast and convient.
Also this approch is OK for my users.

3/ And now I try the same approach with an asp.net-webform.
I cach the datsource for the asp.net dropdown. But even so, in this
case the customers asp:dropdown loads slowly on every postback I make.
I think now that my users used to my userfriendly Access-forms wouln't
like the move from the Access app. into an asp.net app.

Thinking about if there is a possibilty to cach comboboxes and
dropdowns on the client the way Access-projekt-asp-forms can do with
Visual studio dot net.
Does anyone know about these issues?
BigOlle

I am also an Access person who is learning ASP.NET
I recommend you get a book: "Microsoft asp.net web matrix starter kit".
I bought it for the info on the FREE Microsoft development environment
Web Matrix (a sort of Lite version of Visual studio . NET). IT also has
good info on caching records read to solve just the kind of issue you have.

I got my copy for about $8 including shipping through Amazon, from one
of their 3rd party vendors.

Bob

[olle]

thanks for your tip.
I problably by this book, if you think that it is userful even if I am
installing Visual Studio dot net instead of webb Matrix.

a question: As I plan to install visual studio dot net on my computer i
wonder if Webb Mattrix can be installed on the same computer.

But I still don't mind getting some more code tip on this issue on
caching asp.net dropdowns on the client

[billmiami2]

ASP.NET comes with all kinds of caching options You can cache entire
user controls or simple objects like datasets. You can also use the
session and application objects to store objects. However, objects
don't get cached by themselves--you have to specify the caching.

The new .NET framework includes the ability to detect when the
underlying data has been changed so that the cached data is always kept
in sych.

Any beginning ASP.NET book will cover the large number of caching
options available.

Bill E.
Hollywood, FL

[olle]

Well bill.
Have looked about caching in :
Mircosoft.net: Deposito: "Building web solutions with asp.net and
ado.net"
and
Sams: Chris Payne: "Teach yourself ASP.NET in 21 days"
and I haven't found anything about caching dropsdowns on the client in
theese books.
Only how you cashe the datasource for the dropdown.
Maybee you know about some good books on this issue?

[olle]

Well bill.
Have looked about caching in :
Mircosoft.net: Deposito: "Building web solutions with asp.net and
ado.net"
and
Sams: Chris Payne: "Teach yourself ASP.NET in 21 days"
and I haven't found anything about caching dropsdowns on the client in
theese books.
Only how you cashe the datasource for the dropdown.
Maybee you know about some good books on this issue?

[billmiami2]

Caching on the client wouldn't make much sense because your client is
the browser. You'll need to take care of caching on the server, which
will benefit all users simultaneously.

In my apps, I use a user control for all dropdowns and I built into it
the ability to cache the source dataset automatically as well as store
the selected value in a session variable. If I wanted to, I could also
store the entire control in cache.

Either of these methods (caching the source dataset or caching the user
control) would work fine for you.

Bill

ol**@ylm.se wrote:

Well bill.
Have looked about caching in :
Mircosoft.net: Deposito: "Building web solutions with asp.net and
ado.net"
and
Sams: Chris Payne: "Teach yourself ASP.NET in 21 days"
and I haven't found anything about caching dropsdowns on the client in theese books.
Only how you cashe the datasource for the dropdown.
Maybee you know about some good books on this issue?

[olle]

Hi again Bill.
bi********@nets cape.net wrote:

In my apps, I use a user control for all dropdowns and I built into it the ability to cache the source dataset automatically as well as store the selected value in a session variable. If I wanted to, I could also store the entire control in cache.
Either of these methods (caching the source dataset or caching the user control) would work fine for you. hm.. As cashing the dropdown datasource with 2000 records is too slow I
am thinking of cashing the user control,( Id = "mydropdown-contol"...)
Is this the way to do it:
1/Make a page with the drowdown-control with an outputcache on the
whole page.
2/ Save this file with the name:
"mydropdown.asc x"
3/ Then I use this contol in another page, called for exampel,
"MyUpdateForm.a spx" , where the whole database is updated and ...

Is this approach the way you do it?
/Regards Big Olle
Bill

[billmiami2]

Caching a dataset with 2000 records would be lightning fast. What
makes you think that it would be slow?

I always cache the dataset. I make it part of the way the control
operates. I typically include a boolean property that if set to True
causes the control to cache the dataset and to look in cache for the
dataset when it loads.

I haven't yet had any good reason to cache the entire control.

Bill

[olle]

Hej again.
Here is my tuturial asp.net file.
By default I run a sql-query that returns 16459 Records.
I Cache the whole recordset.
Before i Added the dropdown with 2000 records
this application worked fine.
When I click to get the next record, the dropdown loads slowly every
time even as i have cached it's datasource.
here it is: (hope you understand it how it works even if texts are i
Swedish)
http://databas.ylm.se/olle_test/saml...ing_cache.aspx
/Regards BigOlle