Recent content by arian

Hello, what will be the issues if a db is not spit in FE-BE, and is being used simultaneously by 2-3 people? I would like to understand the operational need behind not splitting the db. Is Splitting a matter of product specification or it is just a *better* way to handle the data entry? Is it...

But, yet, I have recently read a thread with a similar issue. But I cannot recur to the solution which has reference to the "utteraccess" site

Thanks Paul, Before posting my question I had aleady read many threads regarding the BE security. This is why I wrote "..no other way.."

I assume that there is no other way to hide the tables in the BE than to set a password, isn't it so? And If I set a password, won't create a trouble each time users insert new data?

Dear CJ what kind of identifier is the "PtrSafe" ?

I use Access 2007. I have a db split in FE(forms, queries, vbcode) & BE(tables only). I want users not to be able to view or explore the tables, the queries, the form design and details, in both Ends. Unfortunately, even disabling via VB code the menus, the db window, the tool & status bars...

The Issue That I described is solved. It was the user that has stored locally the db, and had updated it on his pc. So, no mystery any more... Thank you for your interest in my solving the case.

Currently the users have only the main db (an accde), on a shared drive. It is there that one has added data. And I am an administrator. Wasn't I supposed to be able to view the data into the tables? Can't users update the db since there is no simultaneous access in it?

Users should not at all have any acces to the code, form/tables/queries design and details. Users should ONLY enter data. I already have tried possible solutions by splitting the db to BE-FE (I missed to mention it). However, the restrictions that I want to apply to the users do not apply...

I have created a db having forms, queries, modules apart the tables. This is for common use for a work group. As I want users to only use the forms, and no access to anything else, I have included restrictions, either in the settings of access or by VB code and finally creating a accde (no...

Hello! No barrier will be a wall :)