On Aug 8, 12:08 pm, "Cor Ligthert[MVP]" <notmyfirstn... @planet.nl>
wrote:
The thought crossed my mind today that I should definitely create a
backup in any case - but is the risk really all that high? I mean,
any higher than any other disk access task. I'm assuming you're
referring to a SQL database having some kind of error-checking in
place.
If I could I might ;-)
At the very least all this faffing with tables is helping me get my
head around a proper relational database concept. Not something I've
worked with much before...
Thanks
Bennett
wrote:
Bennet,
>
A dataview is a property from a datatable (called the defaultview) but you
can create more and then they are called dataview.
>
A dataset is a wrapper as you know around datatbles.
>
Be aware that you are busy with a dangerous project, the change that your
dataset on drive becomes corrupted while writing or whatever is high.
>
A dataview is a property from a datatable (called the defaultview) but you
can create more and then they are called dataview.
>
A dataset is a wrapper as you know around datatbles.
>
Be aware that you are busy with a dangerous project, the change that your
dataset on drive becomes corrupted while writing or whatever is high.
backup in any case - but is the risk really all that high? I mean,
any higher than any other disk access task. I'm assuming you're
referring to a SQL database having some kind of error-checking in
place.
>
Better try an SQL database (the SQL Express one is excelent to replace your
dataset (xml file) on disk.
Better try an SQL database (the SQL Express one is excelent to replace your
dataset (xml file) on disk.
At the very least all this faffing with tables is helping me get my
head around a proper relational database concept. Not something I've
worked with much before...
Thanks
Bennett