Post splitting - Accessing Access 2003 while other users have 2002

E

Emily

I have searched through previous posts however I cannot find any specifically
relating to my question...

I have split a database in 2000 format, and loaded the front end onto 3
computers (one is 2003 and 2 are 2002). I have used the link manager on all
machines to relocate the backend. This worked fine. The backend is located on
my hard drive in a shared folder with full access to everyone. The database
works fine independently on all machines. And works well when the 2 machines
with 02 are running the database concurrently.
However, if I am entering any data on either of the machines running 02,
when you try to open the database on the machine running 03, there is a
message something along the lines of " the file abcdef.mdb_be is currently
being accessed by another user" ,therefore preventing the database being
opened on that machine, but no disruption to the machine running 02.
Visa versa, if the machine running 03 is opened first it runs fine, and the
02 machines CAN open the file also with no messages, but cannot actually
enter any data.
What have I done wrong, please help!!!
Thanks
 
D

Douglas J. Steele

What permissions do your users have on the folder where the back-end exists?

They need Change access: Read, Write, eXecute and Delete. This is because
the first user in causes a locking file (.LDB) to be created in that folder,
subsequent users update that file, and the last user out deletes it. There's
no way to change this behaviour.
 
A

Arvin Meyer [MVP]

You could have only a very few small records and the page lock is affecting
them. You should be able to add new records if this is happening.

Or you could have the locks set incorrectly. With the database open go to
Tools ... Options ... the Advanced tab.

Check either No locks, or Edited record.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
E

Emily

I have always had shared full access to everyone.

RE the permissions from what i can see, they are; Full control, change, and
read. These are they only ones available and are all checked. I don't know if
I still need write, execute and delete as Doug suggested?

Some good news though, everything seems to be working fine. I assume the
magic access faries came in over the weekend....

I have a concern about locking file though. Because I have loaded the front
end on to the users desktop, the locking file also appears on the desktop. Is
this right?

I did a test this morning and had users on the 03 and 02 machines at the
same time and both had no probs. But when I entered a dummy entry in the
other user could not see it until she closed down her db and opened it again.
Is this what I can expect to happen with all entries made. ie having to close
the db and open it again to see new information. I was under the impression
that info is updated and available for other users to see without having to
do that....
 
A

Albert D.Kallal

I don't know if
I still need write, execute and delete as Doug suggested?

I don't know about execute..but you need to give users full permissions to
that shared folder. When one says full permissions, that means full
permissions. So, in effect, why guess around here. Give them full
permissions, as that is what is required here. The users need delete rights,
and once you give them that...not much else can be any worse...can it?

Further, you should as a habit give those users a mde.
I have a concern about locking file though. Because I have loaded the
front
end on to the users desktop, the locking file also appears on the desktop.
Is
this right?
Click to expand...

Yes, any time a mdb file is opened, a corresponding locking file will be
created. And, of course a locking file is also created in the back end also.
Those locking files keep track of records edited. You can STILL allowed to
have records and tables in the front end part. In fact, if your front end
links to 5 different backends, then all of them also get a locking file.

You could (or perhaps should) put just a short cut on the desktop, and then
place the mdb (well, hopefully mde) file in a directory of its own.

Often, most programs go in:

c:\program files\YouCoolSalesDataBase\sales.mde

Placing the whole mde on the desktop is not the best, since a user could in
fact quite easily delete it when cleaning up the desktop (of course, I
suppose
if they delete it, they don't hurt the data part (another great reason to
split)).
I was under the impression
that info is updated and available for other users to see without having
to
do that....
Click to expand...

If you just close the form, and then re-open it..you will see the other
entries (you don't have to exit ms-access). If I have a form open with 4
records, and we got 18 other people entering data, if the form updated for
these new records, then I would all of sudden see records jumping in all
over the place. I mean, if I go back to look at the previous record, and
then 10 more records get added, I now can't really navigate with any kind of
sensible behavior here can I? Suppose I go back one record to check
something, and then go forward to the record I was looking at. If 18 other
people are working, then potentially a LOT of records could be entered in
that
time. Navigating back to the next record could mean that MANY MANY records
have been added. So, the new records added by other users are not
automatically loaded into a form until you re-load the form, or requery the
form. Of course exiting, and re-entering ms-access does the same thing as
requering a form.

Of course, from a performance point of view, it is not ideal to simply load
up a form with a zillion records, and THEN have the user look for whatever.
It is generally best to ASK the user what customer (or whatever) before you
load the form. You then edit the customer etc, and then close the form to
return back to the search prompt. The add bonus of this approach is that
after you enter, or edit a name, you close the form, and the data is saved.
Any other user on the system can then also search for, or bring up the
customer. And, since the form is only loading the record you need, then you
save VALUABLE network bandwidth.

You can get some thoughts on searching for a record here:

http://www.members.shaw.ca/AlbertKallal/Search/index.html
 
E

Emily

Thanks, Albert. Some food for thought. Now I have to go and find out what
mde's are all about...

RE to the permissions: Just confirming these are what is applied to the
folder that I have share that containes the BE.
I have given full permisions, the only ones available on my screen are Full
control, change, and read. These are they only ones available and are all
checked. Can you add other permissions like the ones Doug suggested( write,
execute and delete). What do I need to do to get these if this is the case...
 
D

Douglas J Steele

Full Control should be enough. The permissions I describe show my age <g>:
in NT, that's how the permissions are delimited.

The critical thing is that they need the ability to write to the folder and
to delete from the folder. If they can create a Text file in the folder, add
text to it (and save it) and then delete it afterwards, they should be fine.
 
A

Arvin Meyer

Full Control is actually more than enough. It is the maximum available, and
includes the ability to take ownership of a file or folder. The next step
(Modify) and everything below is what I generally recommend. Network admins
will generally balk at allowing Full Control to users.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access Downloads
http://www.datastrat.com
http://www.mvps.org/access
 
Top