Database integrity
in [General]
|
Prev: mail merge currency
Next: Email multiple reports
From: John Spencer on 24 Feb 2010 15:09 One other remote possibility if you are using a linked backend and there are copies of the backend out there for testing, development, or no known reason. The user could be linked to a different backend. John Spencer Access MVP 2002-2005, 2007-2010 The Hilltop Institute University of Maryland Baltimore County Dirk Goldgar wrote: > "Tara" <Tara(a)discussions.microsoft.com> wrote in message > news:DC8BD76B-AFFC-49F9-B8A7-82AD2378522F(a)microsoft.com... >> Thanks Dirk. >> >> I have looked in the tables directly...no data. There is only one delete >> query - it's very specific and limited in scope and doesn't include >> the table >> in question, so I know that's not the issue. I do have cascading deletes >> set, but there is no way to delete the parent record via forms. Someone >> would have had to enter the table directly, which is highly unlikely. >> Which >> basically leaves me with #1. >> >> Thank you. I was a tad upset that the integrity of my design was being >> questioned. I knew I personally had never seen data just randomly >> disappear, >> but I needed to confirm from someone more knowledgeable than myself >> that it >> simply doesn't happen that way. > > > It does not. > > One additional possibility occurs to me. If the data entered was > invalid in such a way that it could not be saved -- missing required > fields, failing a validation rule, no matching record in a related > table, etc. -- then *if* you close the form in code by calling > DoCmd.Close, then the invalid record will be silently discarded and the > form will close anyway. In this case, the user would not realize that > the record had not been saved. > > For this reason, it is important that if you have a "Close" button on > your form, you make sure that the code for that button explicitly saves > the record before closing the form, like this: > > If Me.Dirty Then Me.Dirty = False > DoCmd.Close acForm, Me.Name, acSaveNo > >
From: a a r o n . k e m p f on 24 Feb 2010 17:47 Access / Jet randomly loses data. It's just not a reliable system, not for a single record and a single user. It's time to upsize to SQL Server if you don't trust jet databases -Aaron MCITP: DBA On Feb 24, 7:51 am, Tara <T...(a)discussions.microsoft.com> wrote: > I have someone who says they entered data into a database, but the data isn't > there. Others have entered data into the same database and that data is > there. All users have used the same front-end. Save is automatic when the > form is closed. There are no signs of corruption. > > Is this possible?
From: david on 24 Feb 2010 22:24 You know, I had disappearing data once... I added 'workgroup security' and removed the delete permission from the data. (I gave the user a short-cut for log-in). Within minutes, while I was still sitting there, a user reported an error, caused by the missing delete permission, and conclusively indicating where the missing data was going. In that case, we did not know where the data was going. I thought our instructions and our user interface were clear, but I was wrong. The client thought workgroup security would not help, but they were wrong. The user thought he was following process, but he was wrong. Human error is the cause of almost all data corruption. (david) "Tara" <Tara(a)discussions.microsoft.com> wrote in message news:83693CD9-76E5-4225-9864-CEB70132EA59(a)microsoft.com... >I have someone who says they entered data into a database, but the data >isn't > there. Others have entered data into the same database and that data is > there. All users have used the same front-end. Save is automatic when > the > form is closed. There are no signs of corruption. > > Is this possible?
From: Larry Linson on 25 Feb 2010 01:22 "a a r o n . k e m p f @ g m a i l . c o m" <aaron.kempf(a)gmail.com> wrote > Access / Jet randomly loses data. > It's just not a reliable system, not for a single > record and a single user. Mr. Kempf's statements are both erroneous. Access / Jet does not "randomly lose data", and it is quite reliable for everything from single user databases to properly-implemented multiuser and client-server databases. Larry Linson Microsoft Office Access MVP
From: a a r o n . k e m p f on 26 Feb 2010 17:01
BS - jet doesn't even support security any longer. Jet isn't reliable or a reasonable option for even single-user applications Anything else you claim is just an excuse because you've got a midget- sized db -Aaron On Feb 24, 10:22 pm, "Larry Linson" <boun...(a)localhost.not> wrote: > "a a r o n . k e m p f @ g m a i l . c o m" <aaron.ke...(a)gmail.com> wrote > > > Access / Jet randomly loses data. > > It's just not a reliable system, not for a single > > record and a single user. > > Mr. Kempf's statements are both erroneous. Access / Jet does not "randomly > lose data", and it is quite reliable for everything from single user > databases to properly-implemented multiuser and client-server databases. > > Larry Linson > Microsoft Office Access MVP |