Home All Groups Group Topic Archive Search About

Moving to network drive

Author
25 Sep 2006 10:31 AM
Matt Dawson
I currently have an MDW file with a shortcut and security files. I have also
split this database so that it has a front end.
I need to move these to O:\Csg.
How do i go about it and what do i need to move?
Matt

Author
25 Sep 2006 11:45 AM
Keith Wilby
"Matt Dawson" <MattDaw***@discussions.microsoft.com> wrote in message
news:9F2ABFDB-2329-48EE-A330-F913F7B48FC5@microsoft.com...
>I currently have an MDW file with a shortcut and security files. I have
>also
> split this database so that it has a front end.
> I need to move these to O:\Csg.
> How do i go about it and what do i need to move?
> Matt

Put your back end and mdw files on the server and put a copy of the front
end on each user's PC.

Regards,
Keith.
www.keithwilby.com
Author
25 Sep 2006 2:26 PM
Matt Dawson
Right ok, I have never done this before and am slightly confused.

I hav four files i need to work with. The security (mdw), the back-end, what
i think you call the front end, and then the shortcut that I currently run
off.

The security file and the main database (ie what the shortcut runs off) are
currently on the network. Does the back-end need to be on there too and then
the shortcut on each user's computer?

Matt

Show quoteHide quote
"Keith Wilby" wrote:

> "Matt Dawson" <MattDaw***@discussions.microsoft.com> wrote in message
> news:9F2ABFDB-2329-48EE-A330-F913F7B48FC5@microsoft.com...
> >I currently have an MDW file with a shortcut and security files. I have
> >also
> > split this database so that it has a front end.
> > I need to move these to O:\Csg.
> > How do i go about it and what do i need to move?
> > Matt
>
> Put your back end and mdw files on the server and put a copy of the front
> end on each user's PC.
>
> Regards,
> Keith.
> www.keithwilby.com
>
>
>
Author
25 Sep 2006 2:55 PM
Keith Wilby
Show quote Hide quote
"Matt Dawson" <MattDaw***@discussions.microsoft.com> wrote in message
news:85EE6039-614E-4F1A-AAE4-E4A122108CB3@microsoft.com...
> Right ok, I have never done this before and am slightly confused.
>
> I hav four files i need to work with. The security (mdw), the back-end,
> what
> i think you call the front end, and then the shortcut that I currently run
> off.
>
> The security file and the main database (ie what the shortcut runs off)
> are
> currently on the network. Does the back-end need to be on there too and
> then
> the shortcut on each user's computer?
>

Not quite.  You need the back end mdb (ie tables only) and the mdw on your
server.  You then need a copy of the front end (ie all other objects plus
linked tables) on each user's PC and a shortcut on their desktop in the
following format:

"Full path to MSACCESS.EXE" "Full path to your local front end.mdb" /wrkgrp
"Full path to your workgroup file.mdw"

including the quotation marks.

HTH - Keith.
www.keithwilby.com
Author
25 Sep 2006 3:09 PM
Matt Dawson
Cheers Keith, thats brilliant.

I assume it does not matter where the front end is located on their computer
as long as it is signified in the shortcut target?

Many Thanks

Show quoteHide quote
"Keith Wilby" wrote:

> "Matt Dawson" <MattDaw***@discussions.microsoft.com> wrote in message
> news:85EE6039-614E-4F1A-AAE4-E4A122108CB3@microsoft.com...
> > Right ok, I have never done this before and am slightly confused.
> >
> > I hav four files i need to work with. The security (mdw), the back-end,
> > what
> > i think you call the front end, and then the shortcut that I currently run
> > off.
> >
> > The security file and the main database (ie what the shortcut runs off)
> > are
> > currently on the network. Does the back-end need to be on there too and
> > then
> > the shortcut on each user's computer?
> >
>
> Not quite.  You need the back end mdb (ie tables only) and the mdw on your
> server.  You then need a copy of the front end (ie all other objects plus
> linked tables) on each user's PC and a shortcut on their desktop in the
> following format:
>
> "Full path to MSACCESS.EXE" "Full path to your local front end.mdb" /wrkgrp
> "Full path to your workgroup file.mdw"
>
> including the quotation marks.
>
> HTH - Keith.
> www.keithwilby.com
>
>
>
Author
25 Sep 2006 3:45 PM
Keith Wilby
"Matt Dawson" <MattDaw***@discussions.microsoft.com> wrote in message
news:92B8F0B7-6807-44CC-A258-3534CD7BA9F2@microsoft.com...
> Cheers Keith, thats brilliant.
>
> I assume it does not matter where the front end is located on their
> computer
> as long as it is signified in the shortcut target?
>
> Many Thanks
>

That's right :-)

Keith.
Author
26 Sep 2006 1:06 PM
Matt Dawson
Keith,

I also need to update the tables once a week with new data that comes in. Do
I simply add this to the back-end tables? I dont see how the link from the
network drive (where the back-end is) will link to the shortcut that the
agents run from as there is no link to it within the shortcut target!

Matt

Show quoteHide quote
"Keith Wilby" wrote:

> "Matt Dawson" <MattDaw***@discussions.microsoft.com> wrote in message
> news:92B8F0B7-6807-44CC-A258-3534CD7BA9F2@microsoft.com...
> > Cheers Keith, thats brilliant.
> >
> > I assume it does not matter where the front end is located on their
> > computer
> > as long as it is signified in the shortcut target?
> >
> > Many Thanks
> >
>
> That's right :-)
>
> Keith.
>
>
>
Author
26 Sep 2006 2:32 PM
Rick Brandt
Matt Dawson wrote:
> Keith,
>
> I also need to update the tables once a week with new data that comes
> in. Do I simply add this to the back-end tables? I dont see how the
> link from the network drive (where the back-end is) will link to the
> shortcut that the agents run from as there is no link to it within
> the shortcut target!

It doesn't.  The shortcut is pointing at the front end file and the links
inside the front end point at the back end.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt   at   Hunter   dot   com
Author
25 Sep 2006 3:18 PM
Joan Wild
In addition Matt, you'll need to open the frontend and refresh the links to
the tables in the backend in it's new location.

Just do this in one frontend.  Then copy that frontend to the server.  Then
you need only copy the FE from the server to each workstation (the path to
the backend will travel with it).

The copy of the frontend on the server, is only there for ease of
distribution; no one will actually use that frontend directly.



--
Joan Wild
Microsoft Access MVP

Keith Wilby wrote:
Show quoteHide quote
> "Matt Dawson" <MattDaw***@discussions.microsoft.com> wrote in message
> news:85EE6039-614E-4F1A-AAE4-E4A122108CB3@microsoft.com...
>> Right ok, I have never done this before and am slightly confused.
>>
>> I hav four files i need to work with. The security (mdw), the
>> back-end, what
>> i think you call the front end, and then the shortcut that I
>> currently run off.
>>
>> The security file and the main database (ie what the shortcut runs
>> off) are
>> currently on the network. Does the back-end need to be on there too
>> and then
>> the shortcut on each user's computer?
>>
>
> Not quite.  You need the back end mdb (ie tables only) and the mdw on
> your server.  You then need a copy of the front end (ie all other
> objects plus linked tables) on each user's PC and a shortcut on their
> desktop in the following format:
>
> "Full path to MSACCESS.EXE" "Full path to your local front end.mdb"
> /wrkgrp "Full path to your workgroup file.mdw"
>
> including the quotation marks.
>
> HTH - Keith.
> www.keithwilby.com
Author
8 Oct 2006 11:58 AM
a
Show quote Hide quote
"Keith Wilby" <h***@there.com> wrote in message
news:4517be8d_1@glkas0286.greenlnk.net...
> "Matt Dawson" <MattDaw***@discussions.microsoft.com> wrote in message
> news:9F2ABFDB-2329-48EE-A330-F913F7B48FC5@microsoft.com...
>>I currently have an MDW file with a shortcut and security files. I have
>>also
>> split this database so that it has a front end.
>> I need to move these to O:\Csg.
>> How do i go about it and what do i need to move?
>> Matt
>
> Put your back end and mdw files on the server and put a copy of the front
> end on each user's PC.
>
> Regards,
> Keith.
> www.keithwilby.com
>