Multippel user database

  • Thread starter Thread starter Ubben
  • Start date Start date
U

Ubben

Hello
I have created several databases wich have multippel users simultainusly.
This works quite good, but ones in a while, one user locks the database for
the other useres.
I've done several changes to prevent this lock:
separated data and forms in to databases
data entry in a form with no connection with tabels
all forms with changes not allowed
My question is:
How can I set up-design a database for multippel users-what's correct
 
Ubben said:
I have created several databases wich have multippel users simultainusly.
This works quite good, but ones in a while, one user locks the database for
the other useres.
I've done several changes to prevent this lock:
separated data and forms in to databases
data entry in a form with no connection with tabels
all forms with changes not allowed
My question is:
How can I set up-design a database for multippel users-what's correct
Click to expand...

You want to split the MDB into a Front End MDB containing the queries,
forms, reports, macros and modules with just the tables and
relationships in the Back End MDB. The FE is copied to each network
users computer. The FE MDB is linked to the tables in the back end
MDB which resides on a server. You make updates to the FE MDB and
distribute them to the users, likely as an MDE.

See the "Splitting your app into a front end and back end Tips" page
at http://www.granite.ab.ca/access/splitapp/ for more info. See the
Auto FE Updater downloads page
http://www.granite.ab.ca/access/autofe.htm to make this relatively
painless.. The utility also supports Terminal Server/Citrix quite
nicely.

Tony
 
Ubben said:
Hello
I have created several databases wich have multippel users simultainusly.
This works quite good, but ones in a while, one user locks the database
for
the other useres.
I've done several changes to prevent this lock:
separated data and forms in to databases
data entry in a form with no connection with tabels
all forms with changes not allowed
My question is:
How can I set up-design a database for multippel users-what's correct
Click to expand...

It sounds like you've already "split" your application but it also sounds
like all users are sharing the same front end file. Give each user their
own copy of the front end file and see if that fixes it.

Keith.
www.keithwilby.co.uk
 
MDE is that "run time" version of Access ?
And if so how to i create one ?
Click to expand...

"run time" actually refers to a type of installation of the access program,
not any specific db. Runtime access is a version with no development
capabilities... it has only enough to support running your app on a users
computer that does not have the full version of access installed.

And MDE, on the other hand, is a secured copy of your frontend. It disables
any design changes, and removes all access to the code, preventing anyone
from changing and/or stealing ideas.

Not sure about 07, but in 2003 and before, go to tools, database utilities,
make mde from the toolbar.

Make sure you have everything set exactly as you need it before doing this,
you won't be able to change it after (it will create a new file, not
overwrite your current mdb file, so you will still have your original copy).

hth
--
Jack Leach
www.tristatemachine.com

"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)
 
Thank you thousand :-))
--
Best regards
Ubben


Jack Leach said:
"run time" actually refers to a type of installation of the access program,
not any specific db. Runtime access is a version with no development
capabilities... it has only enough to support running your app on a users
computer that does not have the full version of access installed.

And MDE, on the other hand, is a secured copy of your frontend. It disables
any design changes, and removes all access to the code, preventing anyone
from changing and/or stealing ideas.

Not sure about 07, but in 2003 and before, go to tools, database utilities,
make mde from the toolbar.

Make sure you have everything set exactly as you need it before doing this,
you won't be able to change it after (it will create a new file, not
overwrite your current mdb file, so you will still have your original copy).

hth
--
Jack Leach
www.tristatemachine.com

"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)
Click to expand...
 
Back
Top