i was typing in microsoft access,but one time power supply was not coming to CPU so it was switch OFF.but the typing data was not erasing when i SWITCH ON again(more over the data not saved before cutting of power supply).so my doubt is how the data are saving without any saving comand....
-
-
In short, Access saves a record by default when you move to the next or previous record in a table at any stage after editing.
Maybe you moved records without noticing or something and then the power suddenly went belly up!!
If the power continues to be a problem dont worry to much about saving records because Access is a master at understanding what do with an open database... when the power suddenly goes off..........it corrupts
Welcome to Bytes by the way :)Comment
-
No "Save" command is needed in Access in order to save data. When you move from one record to another the frist record is saved. When you close a form the current record is saved. That's simply how Access works.
If you want to give the user the option of saving or dumping newly entered data, you can throw up a messagebox in the Form_BeforeUpda te event asking whether to save it or not and act accordingly.
Linq ;0)>Comment
-
Oh the joys of JET and abrupt power loss, I/O or even sneezing. I had an Access db corrupted beyond any repair at least 4 times the last 2 months. That was a note to self to wait a few minutes more before I pull the USB stick from the PC.Comment
-
Alternatively, the Safely Remove Hardware option might be a good idea before removing a USB device in all cases. I can't imagine where you ever got the idea that simply removing it from the drive was a good idea. It should never be removed with an open Access database of course, but that's not the limit of how not to treat one.Originally posted by robjensComment
-
hehe a open one? nah...it was at least half a minute after closing the application. And safely removing hardware? I dunno...never ever met anyone who does that..same like parking your harddrive. It was ok,but not really a must to start with.Comment
-
So, you've had four corrupted databases in the last two months after pulling out your USB drive without assuring it's first had all the data flushed, yet you still see no reason for flushing the data. That's a hard attitude to understand Rob.
By the way, you're probably too young to remember it, but there was a time when parking the drive heads was actually quite necessary if you wanted to avoid damage. Technology has moved on from there now of course.Comment
-
Meh. Obviously after the 2nd or 3rd time I read more about JET and it's common problem from ancient code. It's quite rare that any files have these problems but what can I say? Are they robust formats, or is JET flawed? Oh well. I was about 9 when LLL the first one came out, with DOS you didn't have to park even though you could, and if I recall correctly it was only in the period around Win 95 that it was a issue.
But anyway you're right of course. I stepped to data objects now but still need to rely on Access because of the environment I produce in at work. There it gets 3 full network backups and some through my code. The corrupted file was never a problem having lost maybe 4 hours work but being able to reproduce the code in 30 mins. So all is well.
Nice discussions though...I like :)Comment
-
Well Rob. Your choice of course. There's little point in simply repeating myself, so good luck :)Comment
Comment