Anyway to prohibit link to non trusted location

dhlao

Registered User.
Local time
Today, 15:06
Joined
Dec 23, 2014
Messages
37
I've add the path in Trust Center - Trust Locations.
Now, every time I link to those tables in the accdb file which inside the trusted location, there's no more warning show again.

But, those not inside trusted location is still prompting the warning message. With a "Open" button that allow user to click on it to link the table.

What I want to do is completely prohibit user link to those accdb's tables which is not in the trusted location. Warning can be prompt, but no "Open" button for them to click. Is that possible ?
 
why would they need to link to any other tables?

other than giving a user a runtime version of access, I struggle to see how you could prevent them just opening access, and linking to a back end. That's what access does.

What you are asking sounds like having excel, but trying to stop a user browsing to a new excel file
 
hello gemma-the-husky,
My purpose is to restrict what file user can open.
The design is to let user to use the frontend accde to choose a backend accdb to open. Then link its tables.
A central storage will be use to store the valid backend accdb files. All the other accdb (even valid), if not store in that central storage can't be open by the frontend accde.
 
the only way would be to give the users runtime access, not full access.

with full access, they can clearly create new databases.

as I say, otherwise it's like giving a user Excel, and then trying to prevent them creating a new spreadsheet.
 

Users who are viewing this thread

Back
Top Bottom