Admin

[Brian]

Our database is designed for multiple users at once. I
am the only one that does any design work. Most often
when I want to do design work it tells me that I don't
have exclusive access at this time so any design changes
won't be saved.

Is there a way for me to kick everyone else off when I
need to do design work?

 

[Tim Ferguson]

Our database is designed for multiple users at once. I
am the only one that does any design work. Most often
when I want to do design work it tells me that I don't
have exclusive access at this time so any design changes
won't be saved.

Is there a way for me to kick everyone else off when I
need to do design work?

Recommended solution is to split the database into ONE back end mdb with
just tables, relatinships and data, and ONE front end mdb PER USER with all
the forms, modules, queries and reports.

You can work on upgrading the user interface on a separate copy of the
front end (with a special back end containing test data, preferably); and
when you want to rule it out, you just copy the new front end over their
old ones.

Advantages: faster for users, safer in terms of file corruption, neater
design/ development for you.

Disadvantages: none come to mind....


HTH


Tim F

 

[TC]

(snip)

Disadvantages: none come to mind....

The relink thing!

TC

 

[Tim Ferguson]

The relink thing!

A dozen lines of code and then forget about it.... <g>


Tim F