I created a DB which is installed (with custom .mdw) on our LAN, accessible
by a shortcut. Users have no trouble using it. I wanted to move the DB to a
laptop of another person in order to do a demo at another location. I copied
it over to the laptop's D drive, logged on as the owner of the PC. Even after
changing the short cut to reflect the new location of the .mdw file and the
DB, got error messages that I didn't have permissions to open it.

Created a new, unsecured DB (logged on as myself) in a folder on the LAN.
Copied that to the other person's laptop. This time, got a message that the
DB was read-only. I finally got the demo version to work by logging on as
myself and copying the newly created file to the laptop.

Can anyone tell me what's going on? I may asked to develop DBs for the other
location and need to resolve this issue. Any ideas?
--
susan

Hi Susan,

This sounds like Operating System permission issue. The logged on user must
have full access privileges to the folder where all the access data files
reside. Another reason why an Access file is read-only is well.. it's been
marked read-only. In explorer, navigate to that file and right-click on it
and make sure the read-only attribute has not been checked.


HTH,
Immanuel Sibero




"Susan L" <(E-Mail Removed)> wrote in message
news:72FDC189-506B-41BD-AE59-(E-Mail Removed)...
> I created a DB which is installed (with custom .mdw) on our LAN,
accessible
> by a shortcut. Users have no trouble using it. I wanted to move the DB to
a
> laptop of another person in order to do a demo at another location. I
copied
> it over to the laptop's D drive, logged on as the owner of the PC. Even
after
> changing the short cut to reflect the new location of the .mdw file and
the
> DB, got error messages that I didn't have permissions to open it.
>
> Created a new, unsecured DB (logged on as myself) in a folder on the LAN.
> Copied that to the other person's laptop. This time, got a message that
the
> DB was read-only. I finally got the demo version to work by logging on as
> myself and copying the newly created file to the laptop.
>
> Can anyone tell me what's going on? I may asked to develop DBs for the
other
> location and need to resolve this issue. Any ideas?
> --
> susan

Thank you Immanuel. When I went to properties of the database and clicked on
Security/Advanced/Owner, I was still listed as the owner of the DB. That
accounted for the immediate problem. However, when we tried copying the DB to
another person's computer for a second time, ownership was transferred to
her. So, maybe this was a one-time fluke--but thanks to your input, I now
know how to fix it if it occurs again.

"Immanuel Sibero" wrote:

>
> Hi Susan,
>
> This sounds like Operating System permission issue. The logged on user must
> have full access privileges to the folder where all the access data files
> reside. Another reason why an Access file is read-only is well.. it's been
> marked read-only. In explorer, navigate to that file and right-click on it
> and make sure the read-only attribute has not been checked.
>
>
> HTH,
> Immanuel Sibero
>
>
>
>
> "Susan L" <(E-Mail Removed)> wrote in message
> news:72FDC189-506B-41BD-AE59-(E-Mail Removed)...
> > I created a DB which is installed (with custom .mdw) on our LAN,
> accessible
> > by a shortcut. Users have no trouble using it. I wanted to move the DB to
> a
> > laptop of another person in order to do a demo at another location. I
> copied
> > it over to the laptop's D drive, logged on as the owner of the PC. Even
> after
> > changing the short cut to reflect the new location of the .mdw file and
> the
> > DB, got error messages that I didn't have permissions to open it.
> >
> > Created a new, unsecured DB (logged on as myself) in a folder on the LAN.
> > Copied that to the other person's laptop. This time, got a message that
> the
> > DB was read-only. I finally got the demo version to work by logging on as
> > myself and copying the newly created file to the laptop.
> >
> > Can anyone tell me what's going on? I may asked to develop DBs for the
> other
> > location and need to resolve this issue. Any ideas?
> > --
> > susan
>
>
>