Alternative to AutoPostback for saving data

[John Saunders]

"p" <abefuzzleduser2@yahoo.com> wrote in message
news:ecvd9KPXDHA.2344@TK2MSFTNGP09.phx.gbl...

> We have an ASP.net app that is copies an existing database program
> functionality, that does not require users to click a Save button after

they

> make changes. To get this user functionality the same in ASP.net, I have
> used autopostbacks for all controls (other than datagrids) to save user

data

> to database when they type in a text field and leave, or click a
> dropdownlist or checkbox. The users normally first search for an item and
> update a few fields then stop using it for a few minutes.
>
> Is there any other way to do this than autopostbacks for each control?

Since the database is on the server, not on the client system, the data will
need to travel from the client to the server whenever they leave a field.
This could be done with a web service.

You might be better off explaining to the users the difference between web
applications and "fat client" applications. They should not expect that
level of interactivity.
--
John Saunders
Internet Engineer
[email]john.saunders@surfcontrol.com[/email]

[p]

I agree that they can't expect the same functionality.

Do you mean setup the web service to provide data instead running database
server side?

Thanks
P
"John Saunders" <john.saunders@surfcontrol.com> wrote in message
news:%23037WRPXDHA.2484@TK2MSFTNGP09.phx.gbl...

> "p" <abefuzzleduser2@yahoo.com> wrote in message
> news:ecvd9KPXDHA.2344@TK2MSFTNGP09.phx.gbl...

> > We have an ASP.net app that is copies an existing database program
> > functionality, that does not require users to click a Save button after

> they

> > make changes. To get this user functionality the same in ASP.net, I

have

> > used autopostbacks for all controls (other than datagrids) to save user

> data

> > to database when they type in a text field and leave, or click a
> > dropdownlist or checkbox. The users normally first search for an item

and

> > update a few fields then stop using it for a few minutes.
> >
> > Is there any other way to do this than autopostbacks for each control?

>
> Since the database is on the server, not on the client system, the data

will

> need to travel from the client to the server whenever they leave a field.
> This could be done with a web service.
>
> You might be better off explaining to the users the difference between web
> applications and "fat client" applications. They should not expect that
> level of interactivity.
> --
> John Saunders
> Internet Engineer
> [email]john.saunders@surfcontrol.com[/email]
>
>

[John Saunders]

"p" <abefuzzleduser2@yahoo.com> wrote in message
news:%23fjNWdPXDHA.2312@TK2MSFTNGP10.phx.gbl...

> I agree that they can't expect the same functionality.
>
> Do you mean setup the web service to provide data instead running database
> server side?

No, I mean set up a web service to send updates back to the database. This
may be less efficient than the postbacks, but at least you wouldn't have the
screen flicker.
--
John Saunders
Internet Engineer
[email]john.saunders@surfcontrol.com[/email]

[p]

John,

Do you mean write a browser client side web services consumer? Did not know
that was possible.

I hate the postback waiting also. I just assumed that even using a web
service, you would still have to do interaction in server code anyway in
next postback event? So to get around postback do you mean client code?

Any sample code?

Thanks
P
"John Saunders" <john.saunders@surfcontrol.com> wrote in message
news:%23jddGgPXDHA.1384@TK2MSFTNGP10.phx.gbl...

> "p" <abefuzzleduser2@yahoo.com> wrote in message
> news:%23fjNWdPXDHA.2312@TK2MSFTNGP10.phx.gbl...

> > I agree that they can't expect the same functionality.
> >
> > Do you mean setup the web service to provide data instead running

database

> > server side?

>
> No, I mean set up a web service to send updates back to the database. This
> may be less efficient than the postbacks, but at least you wouldn't have

the

> screen flicker.
> --
> John Saunders
> Internet Engineer
> [email]john.saunders@surfcontrol.com[/email]
>
>

[John Saunders]

It's not so much a part of the architecture of ASP.NET, as it is a feature
of the architecture of the WWW. In fact, you'd have similar issues
regardless of what kind of client-server application you're building.

The client isn't the server, and vice versa.

--
John Saunders
Internet Engineer
[email]john.saunders@surfcontrol.com[/email]


"p" <abefuzzleduser2@yahoo.com> wrote in message
news:%23rrFg7QXDHA.2384@TK2MSFTNGP10.phx.gbl...

> John,
>
> I guess there is no real solution since it is a feauture of the

architecture

> of asp.net.
>
> I do update everything again after the database update so I should be oK.
> but I still have to test everything with concurrent users.
>
> Thanks
> P
> "John Saunders" <john.saunders@surfcontrol.com> wrote in message
> news:ud1KssQXDHA.2360@TK2MSFTNGP12.phx.gbl...

> > "p" <abefuzzleduser2@yahoo.com> wrote in message
> > news:O0XZmSQXDHA.2200@TK2MSFTNGP09.phx.gbl...

> > > John,
> > >
> > > Do you mean write a browser client side web services consumer? Did not

> > know

> > > that was possible.
> > >
> > > I hate the postback waiting also. I just assumed that even using a web
> > > service, you would still have to do interaction in server code anyway

in

> > > next postback event? So to get around postback do you mean client

code?

> > >
> > > Any sample code?

> >
> > Unfortunately, I haven't used this yet, so I don't have a sample handy.
> >
> > If you can limit your users to IE 5.5 or above, you can use the "web

> service

> > behavior" to access a web service in client script. Otherwise, you'll be
> > stuck with a Java Applet or something.
> >
> > I'm afraid that the real solution is: don't do that!
> >
> > BTW, do you refresh the entire grid whenever the user enters a new value

> in

> > a field? If not, and if there are simultaneous users, there could be
> > concurrency issues.
> > --
> > John Saunders
> > Internet Engineer
> > [email]john.saunders@surfcontrol.com[/email]
> >
> >
> >

>
>

[p]

I did think of the timer which would be good since their data would get
updated more. But if the users entered something and switched forms it would
not get saved. They have a couple forms they use to enter data.

Thanks
P
"MS News (MS LVP)" <sql_agentman@hotmail.com> wrote in message
news:%23H2g3RQXDHA.2516@TK2MSFTNGP09.phx.gbl...

> Can you put a JavaScript Timer or a MetaTag that will postback every few
> minutes?
> Does a Meta tag Refresh or PostBack???
>
> just a thought.
>
> "p" <abefuzzleduser2@yahoo.com> wrote in message
> news:ecvd9KPXDHA.2344@TK2MSFTNGP09.phx.gbl...

> > We have an ASP.net app that is copies an existing database program
> > functionality, that does not require users to click a Save button after

> they

> > make changes. To get this user functionality the same in ASP.net, I

have

> > used autopostbacks for all controls (other than datagrids) to save user

> data

> > to database when they type in a text field and leave, or click a
> > dropdownlist or checkbox. The users normally first search for an item

and

> > update a few fields then stop using it for a few minutes.
> >
> > Is there any other way to do this than autopostbacks for each control?
> >
> > Thanks
> > P
> >
> >

>
>

[MS News \(MS ILM\)]

The user can enter data then spill coffee on their keyboard or kick their
computer
How do we prevent that?


"p" <abefuzzleduser2@yahoo.com> wrote in message
news:uuBSgEeXDHA.2620@TK2MSFTNGP09.phx.gbl...

> I did think of the timer which would be good since their data would get
> updated more. But if the users entered something and switched forms it

would

> not get saved. They have a couple forms they use to enter data.
>
> Thanks
> P
> "MS News (MS LVP)" <sql_agentman@hotmail.com> wrote in message
> news:%23H2g3RQXDHA.2516@TK2MSFTNGP09.phx.gbl...

> > Can you put a JavaScript Timer or a MetaTag that will postback every few
> > minutes?
> > Does a Meta tag Refresh or PostBack???
> >
> > just a thought.
> >
> > "p" <abefuzzleduser2@yahoo.com> wrote in message
> > news:ecvd9KPXDHA.2344@TK2MSFTNGP09.phx.gbl...

> > > We have an ASP.net app that is copies an existing database program
> > > functionality, that does not require users to click a Save button

after

> > they

> > > make changes. To get this user functionality the same in ASP.net, I

> have

> > > used autopostbacks for all controls (other than datagrids) to save

user

> > data

> > > to database when they type in a text field and leave, or click a
> > > dropdownlist or checkbox. The users normally first search for an item

> and

> > > update a few fields then stop using it for a few minutes.
> > >
> > > Is there any other way to do this than autopostbacks for each control?
> > >
> > > Thanks
> > > P
> > >
> > >

> >
> >

>
>