Accessing through desktop shortcut with multiple users

[Guest]

I have a shared drive with a mdb file. I created a desktop shortcut by
right-clicking
and send-to "desktop."

I have two users A and B. They have full control on both the share and
security permissions on this folder and anything underneath this tree.

If a user A has this already opened, user B is not able to open this by
double clicking the shorcut. On the other hand, if user B opens Access first
and then opens the file using "file->open," the file is accessbile.

Does anyone know what causes this and how to fix it?

I've done a bit of research and some people have said the the exclusive
option causes this issue. Luckily, I do not have any "excl" arguments when
access is being opened.
Furthermore, it is certain that an ldb file is created in the same directory
where the file resides.

 

[Guest]

I'd strongly advise that you split the database into front and back ends, the
former containing the forms, queries, reports, modules etc, the latter
containing only the tables. A copy of the front end should be installed on
each local machine.

Access provides a database splitter wizard which will create a separate back
end and links to the tables in the front end. If you change the location of
the backend you'll need to refresh the links with the built in linked table
manager.

As each user opens a separate copy of the front end you won't get the sort
of problems you are encountering at present. Splitting the database has
other advantages too. You can do any development work on a separate copy of
the front end and then simply replace the copies on each local drive, which
can be done over the network. It also enables you to back up just the data
rather than the whole application.

Ken Sheridan
Stafford, England

 

[Guest]

Ken,

Thanks for that reply.

I actually think it's a very good idea to do this as I've read this type of
response when I was doing research on this topic. I wish I had the knowledge
to do this myself but I'm a SA and don't know much about databases.

The thing I'm a bit annoyed about this whole issue is that people were able
to use this without any problems before I upgraded the file server to Windows
2003. Now, I'm not blaming the migration of the servers here but the fact
that they didn't have any of this does raise some questions in my head as to
what is different from then to what I have currently.

For the quickest fix, I've created a batch file to launch access along with
the file and thus far, it seems to be working OK.

 

[Kevin3NF]

Please take Ken's advice to heart. In your current setup, you are begging
for corruption and up to total data loss...

Any Access consultant in your town can split this thing in an hour or two if
you are not comfortable with it.

Hope that helps...

--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm

Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com

 

[Guest]

It comes down to spending money or calling M$ to split this DB. Again, my
function being an SA, I don't have the knowledge but trying to convince the
manager to do this is a bit difficult especially when it was working before
the server upgrade.

Thank you for the kind advices.

 

[Guest]

Its not at all difficult to split the database and you shouldn't need to
spend any money. I think you'll find it easier than you perhaps imagine, but
be sure to make a backup of your current .mdb file first. The following
relates to Access 2002, but it should be much the same in other versions:

Select the Tools | Database Utilities | Database Splitter menu item on the
main database menu bar and then its just a question of clicking the Split
Database button in the dialogue. You'll then find that a common dialogue
opens inviting you to create a new .mdb file with '_be' added to the current
file's name. You can create this in the same folder or browse to another
location. After the splitter has done its work, in your existing file the
local tables will have changed to linked tables.

Each linked table maps to the real table by means of its Connect property.
If the back end file is moved this needs to be changed so it maps to the new
location, but you don't need to know anything of the underlying processes as
the linked table manager does it for you. To use this go to Tools | Database
Utilities | Linked Table Manager. In the dialogue check the 'Always prompt
for new location' check box and click Select All. Browse to the back end
file and click Open in the common dialogue. You should then get a message
telling you the links were successfully refreshed.

Users should not be using the current file while you are doing this of
course, but it only takes a matter of minutes, so downtime is negligible.
Then give each user a copy of the front end on their local drive and create a
shortcut on their desktop to this.

Ken Sheridan
Stafford, England

 

[Tony Toews]

I actually think it's a very good idea to do this as I've read this type of
response when I was doing research on this topic. I wish I had the knowledge
to do this myself but I'm a SA and don't know much about databases.

What is an SA? Systems analyst? System Administrator? Secretarial
Assistant?

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm