I have a backend database with all my tables. I found that other people have links from my backend database to their own databases, allowing them to update, add and delete records. As I haven't found a way to restrict people linking from my backend, is there a way to find out how many databases and their locations within the server are linked to my database?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Linked Tables
- Thread starter Maria1974
- Start date
Guest_imported
New member
- Jan 1, 1970
- 0
Hi Maria
I sympathize. This is exactly the reason to incorporate security asap. How do you know that people are not chopping and changing data, tables and relationships?
Why not set up security and remove the "admin" user (this is the default user). This will prevent anyone unauthorised from connecting to your database.
Another one (which is well worth doing) is slapping a database password onto the database as well (this will slow down anyone thinking about taking advantage of you and your hard-earned work.
Firstly, though, try and do this when noone is around, and make a copy of the database (maybe to CD?). This will ensure that if anything goes wrong, you can always restore the old version. I would suggest doing so after work or during lunchtime when noone is around.
In order to see who is using your database, that depends on the network setup you have. The old Novell Client32 had a "whohas" command which would tell you who has a connection to that database. You can always back the database up to CD, then delete the backend and wait for people to come crying to you! This is cruel, but its no different from the way that they treat you.
Mr Big.
I sympathize. This is exactly the reason to incorporate security asap. How do you know that people are not chopping and changing data, tables and relationships?
Why not set up security and remove the "admin" user (this is the default user). This will prevent anyone unauthorised from connecting to your database.
Another one (which is well worth doing) is slapping a database password onto the database as well (this will slow down anyone thinking about taking advantage of you and your hard-earned work.
Firstly, though, try and do this when noone is around, and make a copy of the database (maybe to CD?). This will ensure that if anything goes wrong, you can always restore the old version. I would suggest doing so after work or during lunchtime when noone is around.
In order to see who is using your database, that depends on the network setup you have. The old Novell Client32 had a "whohas" command which would tell you who has a connection to that database. You can always back the database up to CD, then delete the backend and wait for people to come crying to you! This is cruel, but its no different from the way that they treat you.
Mr Big.
Maria,
Yes, you should immediately implement security on this database. You should NOT use a database password. You should download the "Access Security White Paper" from the microsoft site and read it several times. It is a complex subject but in a case like this you have a real responsibility to the owners of that data to secure it to at least a reasonable degree.
Jeremy =============
Jeremy Wallace
Designing and building Access databases since 1995.
Yes, you should immediately implement security on this database. You should NOT use a database password. You should download the "Access Security White Paper" from the microsoft site and read it several times. It is a complex subject but in a case like this you have a real responsibility to the owners of that data to secure it to at least a reasonable degree.
Jeremy =============
Jeremy Wallace
Designing and building Access databases since 1995.
- Thread starter
- #5
Thanks for the advise... However, my database is secure and nobody can log in unless I have given them access. The problem is not with my database... if you create a brand new database you can link any tables from any databases within the network. Ms Access won't restrict you linking tables, it doesn't matter whether you have been given access to the original database. And that's my problem. The only advise that could help was from Mr Big, who mentioned the type of network that I use, although it's not Novell Client32.
Ideally, I would like something that detects what databases people have added links from my tables.
Ideally, I would like something that detects what databases people have added links from my tables.
Have a look for the appuser file on
This will look at the database's ldb file and list everyone who is in it.
If you go in it at the beginning of the day and stay there all day, the ldb file will not be deleted, so you will be able to get a list of the username of everybody who has opened that file.
Armed with that list you should be able to find them.
Good luck
B ----------------------------------------
Ben O'Hara
----------------------------------------
This will look at the database's ldb file and list everyone who is in it.
If you go in it at the beginning of the day and stay there all day, the ldb file will not be deleted, so you will be able to get a list of the username of everybody who has opened that file.
Armed with that list you should be able to find them.
Good luck
B ----------------------------------------
Ben O'Hara
----------------------------------------
Maria,
You have implemented security incorrectly. A correctly secured database will not allow anyone to link to the tables unless the have suffecient permission to do so. I promise you.
Get the Access Security White Paper and read it several times. The unsecure and resecure your database (MAKE BACKUPS FIRST). Once done correctly, people will not be able to link to your database without you giving them permission. Again, I promise you this is true.
Jeremy =============
Jeremy Wallace
Designing and building Access databases since 1995.
You have implemented security incorrectly. A correctly secured database will not allow anyone to link to the tables unless the have suffecient permission to do so. I promise you.
Get the Access Security White Paper and read it several times. The unsecure and resecure your database (MAKE BACKUPS FIRST). Once done correctly, people will not be able to link to your database without you giving them permission. Again, I promise you this is true.
Jeremy =============
Jeremy Wallace
Designing and building Access databases since 1995.
Keep the users blind.
If possible, relocate your database(BE) to another area.
leave the existing BE in place and update your FE.
Those who linked will eventually (maybe!) discover that they are working with a morgue.
Access security or not, even after securing a db I have found talented individuals who manage to find a way in.
Rhonin
"too many questions, too little time..."
If possible, relocate your database(BE) to another area.
leave the existing BE in place and update your FE.
Those who linked will eventually (maybe!) discover that they are working with a morgue.
Access security or not, even after securing a db I have found talented individuals who manage to find a way in.
Rhonin
"too many questions, too little time..."
- Status
Similar threads
- Locked
- Helpful tip
- Locked
- Question