Got some related links but does not answer my question; Is it possible to prevent users from link the table in FrontendDb? Which is linked to MainDb?

[pedie]

Hi, I am wanting to disable/hide the table in front [Which is linked to MainDb] from being linked. Is it possible to prevent users from doing that?

Thanks in Advance.

 

[xenou]

Pedie, you are completely obsessed with hiding tables. Don't worry about it. But as far as your question goes, if the user can get to the database, they can get to the tables.

 

[pedie]

Pedie, you are completely obsessed with hiding tables. Don't worry about it. But as far as your question goes, if the user can get to the database, they can get to the tables.

hi Xen! Alright! Does hiding table using vba hide table from linking by any chance...?

 

[xenou]

why do you think someone will link a table in your database? (no vba cannot stop it).

 

[pedie]

why do you think someone will link a table in your database? (no vba cannot stop it).

'm happy happy happy...
I just hide the attributes of the table using vba and made accde file then i open some other access file and tried link the table in front end db and nope I cant see the table to link it....This is what i want.

Xen! thank you!
Have a good day!

 

[xenou]

Okay, makes sense - the front end doesn't actually have a table in it, only a link to the table in the back end.

 

[pedie]

Okay, makes sense - the front end doesn't actually have a table in it, only a link to the table in the back end.

I didnt know that in accde file the users are allowed to change the settings to unhide/view system hidden files...but it allowed; I was think once accde file is created nothing can be changed.
so this is kinda not full solution to what i thought i want.

 

[xenou]

Access database security is a long and difficult topic. SyndneyGeek has an article on it:
http://www.mrexcel.com/forum/showthread.php?t=248191

I don't bother with it. I probably would use a server-based database (back-end) if I wanted to create stronger security. For me it's enough to take simple precautions - hide the tables, split the database, don't show the database window, give the users good forms to work with so they can do their work without looking for workarounds and hacks. If your users are the type to hack into your tables then I'm not sure what to say - I don't think I'd use an Access database which such users.

ξ

 

[pedie]

Access database security is a long and difficult topic. SyndneyGeek has an article on it:

http://www.mrexcel.com/forum/showthread.php?t=248191

I don't bother with it. I probably would use a server-based database (back-end) if I wanted to create stronger security. For me it's enough to take simple precautions - hide the tables, split the database, don't show the database window, give the users good forms to work with so they can do their work without looking for workarounds and hacks. If your users are the type to hack into your tables then I'm not sure what to say - I don't think I'd use an Access database which such users.

ξ

Xen, you're right. I am going against the access feature again. By the way that link can be very usefull.

One small quick question; can a macro running triger a vba code with using the form load to triger the vba code?

Thanks again

 

[xenou]

Here's a better article on what I generally employ:
http://www.techrepublic.com/blog/10things/10-tips-for-securing-a-microsoft-access-database/552

If you want to become an expert you can read:
Real World Microsoft Access Database Protection and Security

I'm not sure what you mean by your other question. A form load event can trigger a macro:

Sub Form1_Load()
    Call Macro1
End Sub

Where Macro1 is either a public procedure in a standard module or a procedure in the same form.