Linked Tables

[chr1stoper1]

Hi Folks

I was wondering if you can link a table in two access databases and make the link one way only. So if someone deleted a entry in one table it would not delete it in the other .

We have a database which someone has been accidently deleting entries from a table . I would prefer not to add a password but we keep losing data.

Any help would be much appreciated

 

[arnelgp]

you can use Form and Disallow deletion of record in the form.
you can also add "Audit trail" on deletion of record.
so you will know who is the culprit and forever remove
him/her from the office.

 

[GPGeorge]

Hi Folks

I was wondering if you can link a table in two access databases and make the link one way only. So if someone deleted a entry in one table it would not delete it in the other .

We have a database which someone has been accidently deleting entries from a table . I would prefer not to add a password but we keep losing data.

Any help would be much appreciated

No, that's not how linked tables work.

There is ONE table. It exists in one accdb or in one SQL Server database, etc.

The LINKS only "point" to that one table. They are not "data storage" in themselves. They are little nuggets of information that tell Access where to go to get the real data.

That means if you delete a record using a linked table, it is actually going to that source table and deleting it there. It's not possible, therefore, for any other "linked table" to still see that record which is now gone from the source table.

You can use Arnel's technique to prevent people from deleting records.

 

[theDBguy]

Hi. Do you allow for additions, just not deletions?

 

[Pat Hartman]

Jet (.mdb) and ACE(.accdb) are not secure databases which is one of the reasons so many Access applications use SQL Server or other RDBMS' as the BE.

We're going to need to know a lot more about the application to give rational advice.
1. Is the application locked down so that the users have access to ONLY forms and reports? They should NEVER even see the Navigation pane.
2. Do you have validation in your forms? You might want to add a double check prompt on any delete actions or prevent deletes entirely. Marking rows for delete rather than deleting them is much safer but changing to that in an existing application will require a change to every single query the app uses to prevent most of them from returning "deleted" records and for others to select "active" or "deleted" specifically because sometimes you might need to get to the deleted records.
3. Are you sure that this isn't a malicious user going directly to the BE and deleting rows?
4. You can isolate the BE by using Windows/DOS tricks to hide the BE so that users cannot see it when browsing. You can only get to it if you know it's path and name which of course the FE would.