Can I move a Front/Back End to a laptop?

[Darin]

I have created a database that uses a front and back end. I would like to
move it to a laptop computer. When I do so, the front end cannot locate the
back end ... it tries to look at the network drive it was created on. Is
there a way to copy both databases over and have the link updated
automatically, rather than re-linking the front and back ends? I have to
move this over to my laptop periodically, so it is not just a one time fix.
Thanks

 

[Peter Hibbs]

Darin,

Have a look at :-
http://www.rogersaccesslibrary.com/forum/forum_posts.asp?TID=184
which may do what you want.

HTH

Peter Hibbs.

 

[Arvin Meyer MVP]

Without custom code to relink, the answer is no to "automatically"

If it's just a single instance, it isn't worth the time to write the code
since it only takes 15 or 20 seconds to do it manually.

Go to:

Tools >>> Database Utilities >>> Linked Table Manager

Select all the tables and browse to the location on your laptop.

 

[Jerry Whittle]

You can create a virtual drive on your computer to match a network drive by
using the old DOS subst command.

Subst--Example

The following command creates a virtual drive Q for the path
C:\USER\BETTY\FORMS:

subst q: C:\user\betty\forms

Now, instead of typing the full path, you can reach this directory by typing
the letter of the virtual drive, followed by a colon, as in the following
example:
q:

If you are using long file names for the folders, use quotes.
subst q: "C:\My Databases"

To remove the virtual drive:
subst q: /d

You can also create more than one virtual drive at a time. I have two that I
load automatically on my home machine by putting the command lines in the
Autoexec.bat file.

 

[Rajtomar]

Hi Darin,

I can think of a much simple solution to this. You might have seen how
all installable programes get stored in C/Program files.. Because C/
Program files exists in all PCs so u can

1. Make a New Folder in "C:/Program files" Name it e.g. MyDB.
2.Save both Frontend and backend in this "C:/Program files/MyDB" and
then do the linking
3.Now when u wanna copy the database in ur laptop just Copy the "MyDB"
folder in ur laptop's program file.
4.Make a shortcut of front end on desktop.
5.Tell me if u need to link it again...


Raj Tomar
....Sometimes We Need To Think Simple...

 

[Douglas J. Steele]

Of course, that won't work under Vista (or Win 7) because they won't have
the necessary permissions under My Programs.

 

[Darin]

When I created the database, it was in my network directory
"G:\FIN\Common\YearsOfExperience".
I went out to my "C:\Data" directory and added the following folders
FIN\COMMON\YearsOfExperience. I was then able to ust the Subst command to
create a virtual G: drive with this path ...

It is working now thanks!

 

[Darin]

Thanks for the simpiler solution ...

 

[David W. Fenton]

m:

I can think of a much simple solution to this. You might have seen
how all installable programes get stored in C/Program files..
Because C/ Program files exists in all PCs so u can

C:\Program Files does NOT exist on all PCs. My desktop computer has
the programs in D:\Programs, and there are no programs at all on the
C: drive, which is dedicated entirely to the OS and swap file.

Indeed, the user profiles are not on C: either -- they are on the E:
drive, which is the data drive (profiles hold user data, so
logically should be on the same partition as user data).

Secondly, Vista uses C:\Programs (though it virtualizes that as
C:\Program Files in order to accomodate programmers like you who
have made incorrect assumptions about where information is stored on
the computer), and its virtualization can break Access MDBs stored
there.

1. Make a New Folder in "C:/Program files" Name it e.g. MyDB.

This is bad practice. The programs folder is read-only for
non-administrators and is not where Access files should ever be
stored.

2.Save both Frontend and backend in this "C:/Program files/MyDB"
and then do the linking
3.Now when u wanna copy the database in ur laptop just Copy the
"MyDB" folder in ur laptop's program file.
4.Make a shortcut of front end on desktop.
5.Tell me if u need to link it again...

Terrible, terrible advice, though the principle is sound, i.e., if
you can install in the same drive/path location on both, you won't
need to relink.

 

[R S TOMAR, EAR-3]

C:\Program Files does NOT exist on all PCs. My desktop computer has
the programs in D:\Programs, and there are no programs at all on the
C: drive, which is dedicated entirely to the OS and swap file.

Indeed, the user profiles are not on C: either -- they are on the E:
drive, which is the data drive (profiles hold user data, so
logically should be on the same partition as user data).

Secondly, Vista uses C:\Programs (though it virtualizes that as
C:\Program Files in order to accomodate programmers like you who
have made incorrect assumptions about where information is stored on
the computer), and its virtualization can break Access MDBs stored
there.


This is bad practice. The programs folder is read-only for
non-administrators and is not where Access files should ever be
stored.


Terrible, terrible advice, though the principle is sound, i.e., if
you can install in the same drive/path location on both, you won't
need to relink.

I completely understand you and appreciate the way u have brought out
the terrible factors of my advice, but as Mr Darin wanted the DB just
to shuttle between "his" PC and "his" laptop (on which he has
administrator access. I suggested the solution just for that and not
to shuttle the DB on any PC in the world. When I said C:/Program files
- I actually meant a folder which is same on his desktop and laptop.
It could be on any damn drive and any damn folder.

And by the way, Mr Darin is happy that his problem is solved....
Cheers...
Sorry for giving a Dumb advice, if it was one...

Raj Tomar
Simplicity is the ultimate sophistication. --- Leonardo da vinci

 

[David W. Fenton]

:

And by the way, Mr Darin is happy that his problem is solved....

My point of view is that your answer goes into the archive at Google
Groups and it's better if it doesn't recommend procedures that are
limited in applicability, but that give caveats as to the drawback.
Someone else with the same problem may be working with a different
version of Windows or with different paths, and they need to know
that the specifics of your suggestion may be radically different.

Again, though, the *idea* is sound, as long as the same path is
available on both PCs. I would recommend against using any location
that is read-only for user-level logons, though.