William
Tue Apr 27 18:46:56 CDT 2004
If you call fill on a dataadapter, it's going to open a connection in one
way or another (the actual physical implementation depends on the provider.
Using Excel as a datasource will have a different implementation that oracle
for instance).
To that end, I'm not sure I understand the question, but if the users are
only doing select statements, concurrency isn't going to be a problem.
Furhtermore, however the thing is structured, you can trap a Concurrency
exception and ADO.NET will raise one so you can respond to it however you
want. That's actually one reason that using the DataAdapterconfiguration
wizard is preferable to a commandbuildeer (one of the reasons) b/c you have
more control over concurrency
If I misunderstood your question, please let me know.
Cheers,
Bill
"Almenares" <anonymous@discussions.microsoft.com> wrote in message
news:6D3BBA6A-F517-41B6-BBB9-2C15FDBADE32@microsoft.com...
> When you use a fill method of the data adapter, it does a connection to
the database, exist 3 mechanisms for avoid this.
> 1. add the dataset to session var
> 2. put the dataset in the view state
> 3. doit a cache.
>
> whell, my doubt is if I can put the dataset in Xml at the Web server, and
only read for this, and all users read from this xml. it brings within a
concurrency problem at the time to read.
>
> thanks.
>