Question Working with the accde (access 2007)

[arian]

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 single solution suffices to obtain all the restrictions).

• the vb code restricts the db window the status & tool bars, full menu and special keys
• the settings restrictions include the hiding of the objects and the navigation pane.

When the db in use, a user can add records via a form, saves them and proceeds to the next record. The autonum of the record increases.

(The user can exit via another form, not the one that is used to add records).

However when I login as admin (the restrictions do not apply), I can only see the records that I have inserted, not the users.
Why this?

 

[pbaldy]

At a guess, you (and possibly everyone) have a stand-alone copy of the db. In a multiuser environment, the db should be split. Each user would have a front end with only forms, reports, etc. A single back end would have the data and would be located on a server or common location.

http://www.granite.ab.ca/access/splitapp/index.htm

 

[arian]

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. This is a big issue.

 

[pbaldy]

I'm not clear on what you and the users have. If you each have your own copy, you'll never see each others data.

 

[arian]

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?

 

[arian]

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.

 

[pbaldy]

Glad you sorted it out.