Why do files in database disappear?

[Guest]

Our database stores personnel information for approximately 23,000
individuals. On occasion, complete files disappear. We are pretty sure that
none of us are deleting these...why would we when so much of what we do is
dependant on this information?...it makes more work for us. Has anyone had
this problem before?

 

[Trey Davis]

someone in your orginization is malisciously deleting the records. It's
probably someone you trust. Interrogate this person immediately, and then
fire him/her.

 

[Jason Simmons]

thanks hitler

more likely, someone is accidently deleting things.

 

[Trey Davis]

Bull S**t !

If SOMEBODY doesn't stop this criminal, the company will pay

 

[Guest]

First we need to make sure that we are singing from the same sheet of music.

A file is something like a .MDB file that you would see in Windows Explorer.
If a .MDB file disappears, the database would not open.

A record is information about one thing. For example your employee table
would have things like EmployeeNumber, FirstName, LastName, DateOfBirth,
SSAN, etc.

A table holds records. For example the Employee table would have all the
employee records. The Offices table would have records about all your
offices. A missing table would be a major problem.

Which of the above have gone missing: Files, Records, Tables, or something
completely different?

BTW: Don't listen to Troll Davis.

 

[dbahooker]

Access MDB isn't a realiable data source.

I would spit on the people that wrote an app using MDB.

SQL Server is a great backend; and Access Data Projects are a vastly
superior solution.

-Aaron
ADP Nationalist

 

[dbahooker]

BTW, don't listen to MDB-wimps

-Aaron
ADP Nationalist

 

[Joseph Meehan]

Our database stores personnel information for approximately 23,000
individuals. On occasion, complete files disappear. We are pretty
sure that none of us are deleting these...why would we when so much
of what we do is dependant on this information?...it makes more work
for us. Has anyone had this problem before?

I would suggest that the most likely issue is someone accidentally
deleting records.

This is one reason it is usually a good idea to assure records are not
really deleted. Often the best choice is to make a record inactive and then
hide it from most users. Also note that records are not really deleted unit
a compact of the database is done. However getting those deleted but not
really deleted records back is not easy, as I understand it.

I would suggest a three part process. First make sure everyone accesses
data ONLY through a form designed for them. That form should contain a
warning about possible deletes and a clear and easy way to back out of the
process. We once had to create three levels of warnings for one of our
administrators who was a little too fast to delete. That was not with
Access. With Access it is a better idea to not let any user to actually
delete data, rather it should be marked as inactive and filtered out so they
can no longer see it, but you can retrieve it if needed. I would suggest
adding a date deleted as well.

 

[aaron.kempf]

and of course; don't use a flaky-ass database engine.

with SQL Server you have a LOT better control; including contraints and
triggers.. let alone PERMISSIONS.

MDB is for retards and babies.
spit on anyone that uses it.


-Aaron
ADP Nationalist

 

[Joseph Meehan]

and of course; don't use a flaky-ass database engine.

Having another bad day?

I suspect that if you had ever really learned to use Access properly,
you would understand how foolish your comments really are.

 

[Larry Daugherty]

Take frequent backups and be sure not copy the backups out to another
folder. That way when you become aware that data is missing you have
some hope that the missing data might exist in one of the earlier
files.

Keep after the problem until you find the cause. Access typically
doesn't arbitrarily delete data. If you can't shake the idea that it
might be malicious activity Allen Browne has an audit utility model on
his site.

HTH

 

[aaron.kempf]

I'll bet that if you knew how to use Access properly; you could get an
immigration visa to a REAL COUNTRY, like the US for example.

All I know is that you kids talk about the same problems; you sit
around and deal with the same shit.. but i've had 10 years of MDB
experience; and I just flat out ****ing hate it.

it's not reliable. it's not scalable. it's not secure.
it's not a viable option.

I can outdevelop ANY mdb developer; using Access Data Projects; with
one hand tied behind my back.

LITERALLY.

-Aaron

 

[aaron.kempf]

you mean, a different HARDDRIVE or MACHINE, right?

I mean; what's the point of taking your eggs out of one basket and then
gently placing them back in the same basket?

-Aaron

 

[Larry Daugherty]

The first line of the previous post should read:

Take frequent backups and be sure to copy the backups out to another
folder.

HTH