WebApplication - DataSet Navigation HickUp

  • Thread starter Thread starter Martin
  • Start date Start date
M

Martin

Hi!
I'm new to ASP.NET WebApplications and wonder whether I've missed
something out when programming it. I'm grateful for any hints to this
problem!

Thanks very much for your efforts!

Martin

Description:
I'm running a Webapplication connection to SQL Server 7 using a
DataSet.
The DataSet is stored on the client. The application works ok
initially e.g. I can browse through the records back and forwards with
Previous and Next.
The variable that holds the currentRow value is declared as 'Shared'
(in case this is important to know).

Trouble starts when I run the same application on a different client
machine on the network at the same time. When I browse through records
on Client B and then go back to Client A and e.g. click Next, it jumps
records. It often goes to the last record in a recordset consisting of
5 when clicking Next although it was only at the second record and
should have gone to the third. Any subsequent Next click behaves
normal until I go back to Client B and change the current Record. At
this point the problem also occurs on Client B since I've changed the
current row on Client A.
It's like that both clients interfere with each other, although the
DataSet is stored locally on each of them??
 
Don't take my word for it. But I think a dataset cannot
be local to a client machine. I don't know much about
this, but it doesn't sound logical that your web browser
is showing something that is being picked up from your
own harddisk. No way.

The data set is created at the server and the asp.net
application running AT THE SERVER picks up some records
from the dataset and shows it in your screen in HTML
format. So as far as the client is concerned, it just
displays whatever that comes down in HTML format, so no
processing is done there.

And why did you 'share' the variable that holds the
current value? try not doing that
 
Michelle Stone said:
Don't take my word for it. But I think a dataset cannot
be local to a client machine. I don't know much about
this, but it doesn't sound logical that your web browser
is showing something that is being picked up from your
own harddisk. No way.

The data set is created at the server and the asp.net
application running AT THE SERVER picks up some records
from the dataset and shows it in your screen in HTML
format. So as far as the client is concerned, it just
displays whatever that comes down in HTML format, so no
processing is done there.

And why did you 'share' the variable that holds the
current value? try not doing that
Click to expand...

Hi! Thanks for replying. I've the dataset stored in the page. Thought
this would be locally to the client to minimize transfers for
roundtrips. Isn't it?

I've done a bit more investigating why it might conflict and I think
storing the dataset on the server and using session state might help.
However, using session state is another science for itself. I just
can't get to see my assembly in the assembly list at START-CP-ADMIN
TOOLS-FRAMEWORK CONFIG as described in MSDN documentation. Tried to
add it but then it says that my assembly needs a strong name etc. Done
that all! Still can't add it.

I hate .NET. My cat does too.
 
Back
Top