Re: Deleting rows from an unbound gridview

Tech-Archive recommends: Speed Up your PC by fixing your registry

"Greg" <spammesilly1@xxxxxxxxxxx> wrote in message
news:1170416775.481740.55050@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

There are 2 relevant tables in the database, lets call them
masterSchedule and actualSchedule.

OK.

The masterSchedule table can never be edited by my part of the
application.

So what's the point of it...? E.g.

1) User fetches a dataset from masterSchedule, makes some changes, and saves
the changes into actualSchedule.

2) masterSchedule is not modified since "The masterSchedule table can never
be edited by my part of the application."

3) User fetches the same dataset from the masterSchedule - aren't they back
where they started...?


.