Re: Linked Tables Losing Data
- From: "lewie" <lewis.krause@xxxxxxxxxxxx>
- Date: 5 Oct 2006 15:04:47 -0700
Gary Robinson has a good book on security. It has limited to full blown
..
It might be worth investing in to tighten things up a bit. It has
sample code, a logging form that keeps track of who was in what table
at what time. You might be sure you use forms in front of all your
queries and lock the back up with the startup form and proceed from
there.
Just my 2 cents worth.
Lewie
Jerry Whittle wrote:
I submit that Access is not losing records. If you network is unstable, the
network is losing records. Consider this: I you are working on a Word
document out on the network and the network crashes, did Word lose your
changes?
If your users are doing a Ctrl + Break to stop a query, they are messing up
Access and could leave some tables in an unstable, maybe even corrupted,
state. Again I submit that Access is not the cause of the problem.
You could possibly avoid some of these problems by going to a more
industrial strength database like SQL Server or Oracle. Access is not a
client/server database in that the computing is done on your PC whereas the
other two mentioned above do their work on the server. A network problem
would not necessarily stop the database from completing its task. Also with
Oracle you need to commit changes. Normally if someone stops a update,
delete, or append query while it is running, the changes are not commited to
the database.
In all cases, even with SQL Server and Oracle, nothing beats a recent,
complete backup!
--
Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
"Gertrude" wrote:
Access databases DO lose records. It happens to my databases sometimes
(especially where the network is unstable or where users use Ctrl Break to
stop a query). I always make sure that I can restore records from backups,
but I would like to know why Access does this.
"Jerry Whittle" wrote:
Databases , not even Access, just don't lose records. Some possibilities:
1. You are linking to the wrong BE MDB file. I've done this.
2. Other users are deleteing records. Seen that.
3. The network drive crashed or something happened to cause a restore from a
backup. They just forgot to tell you. Been there too.
4. Access is running into a severe, persistant corruption problem and is
dropping records when repaired. If so somebody should see this happening. Not
likely.
5. As David Cox wisely mentioned, you are mistaken about the number of
records or querying the records incorrectly. The guy who looks at me in the
mirror while I'm shaving has done this.
--
Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.
"Andy" wrote:
Hi there, I have a number of databases that have linked tables back to
Database A so as not to duplicate tables and fill up servers. In these
databases, I have run a number of queries some of which are based on the
table from Database A.
On returning to the table in Database A, I am frequently finding that this
core table has lost records, dropping it to a total of 10,000 or 20,000 rows
instead of circa 60,000.
None of the queries/work I am doing should affect this core table, so why is
it losing records?!?! If I haven't realised that records have gone missing,
obviously all of my other work is completely futile!!!
Access problem?
.
- References:
- RE: Linked Tables Losing Data
- From: Jerry Whittle
- RE: Linked Tables Losing Data
- Prev by Date: Re: Lookup fields - Yes or No?
- Next by Date: Re: Stand alone database
- Previous by thread: RE: Linked Tables Losing Data
- Next by thread: RE: Linked Tables Losing Data
- Index(es):
Relevant Pages
|
