linked tables are R/O on one machine and R/W on another, why?

[Guest]

I have a front end and a back end of Access 2003 running on a my local
machine. Front end is linked to back end tables by the network address
(\\MyLocalMachine\C\DB\Mydb.mdb). I allow the front end to be accessed by
others on my network. When I access the front end, all (linked) tables are
R/O, all other users who access the front end via the network have R/W access.

The only way I found to have R/W access on my local machine is by linking
the tables locally (C:\DB\Mydb.mdb) but then the network users get the
following error: Run-time error '3044' C:\DB\Mydb.mdb is not a valid path.
Make sure that the path name is spelled correctly... etc.

I have recently upgraded a computer. This application used to run from an
older computer. I checked on the older computer, the address of the linked
tables (I checked via the Linked Table Manager) was the network address. Now
when i use the network address all other computers can run this application
with R/W, only the local machine runs it with R/O permissions...

Please help

 

[dbahooker]

uh because MDB isn't reliable enough for real world use.

use sql server or msde-- i mean-- access data projects rock

it's just as easy to write a sql view or stored proc but it's faster
and better

-aaron

 

[david epsom dot com dot au]

This is a network permissions problem. It may be that
you are not logged in correctly, or that your personal
permissions have changed, but from what you say, it
sounds like your new computer has not been correctly
added to the domain.

Try logging in from a different computer. If you are
ok, the problem is with the way your new computer
has been added to the domain.

Try getting someone else to log in using your new computer.
If they have the same problem, the problem is with the
way your new computer has been added to the domain.

(david)

 

[Guest]

It was a permission issue. Had to go into properties. Ended up going to
'Sharing and Security' and correcting the permission properties on the new
computer. THank you David for pointing to the solution.

HT