Linking to different back ends & Access 2003 Upgrade

  • Thread starter Thread starter AHopper
  • Start date Start date
A

AHopper

I have database with the front end on drive C of a
workstation that I use for developing and the back end on
a network. Presently, the database is small enough for the
back end and front end to fit on a CD. The front end opens
to a switchboard and when the switchboard opens a hidden
form opens that is linked to a table in the back end. (The
form is always open and linked to the back end.)Recently I
purchase a notebook computer (which will replace my
workstation) and now I would like to do some developing on
the notebook off site. I need to be able to link to the
back end on the network and to a copy of the back end when
I want to work off site. How can I do this?

Are there dangers in doing this?

My workstation has Office Developer XP and the notebook
has Access 2003 with the Visual Studio Tools. I want to
experiment with Access 2003 before I remove my workstation
and commit to Access 2003 on the network. I would
appreciate any insight into the differences I will find
with Access 2003 and any problems I should watch for.

Thanks

Allan
 
I do this all the time.

The network backend is located on a drive we have mapped to S:
S is mapped to \\ourserver\trades
with a subfolder called Data
so the real path is \\ourserver\trades\data
and the front end refers to s:\data


On my non-networked machine I have shared a folder called
c:\development\ as development
It has a data folder in it
c:\development\data

When I am ready to work on the database I run a batch files that says:
subst s: c:\development

Now there is a temporary s: drive on my PC, with an s:\data folder where I
put a copy of the back end from the server.
Since I am not connected to the server this is the only S: drive it knows
and the front end works as though it's looking at the server.
I have done this with all versions of Access going waaayyy back!

HTH
Mich
 
Mich

My database back end "AP_be.mdb" is on "Access
database 'Fs2\Data'(L:)". There is no data folder.
If I understand correctly I need to get a temporary L
drive on my Notebook and put a copy of the back end in it.
How do I create the temporary L drive?
How do I run a batch files?


Thank you for your patience and help.

Allan
 
Here's one way:
Create a folder on your notebook called
c:\Development

Right click on that folder and select Sharing
Shared as should say DEVELOPMENT
So now this folder is shared as DEVELOPMENT

In Notepad, create a new file and place this line in it:
subst L: c:\development
Save the file as LDrive.bat

Create folders under c:\development so that you now have:
c:\development\Fs2\Data

If you look in Explorer and look for an L: drive you should not have one.
Double-click the LDrive.bat file
Now look in Explorer, you will see an L: drive with an Fs2 folder and Data
subfolder.
Put your copy of the backend there, same as on the server.

Put your front end somewhere, it doesn't matter where, as long as it knows
the data is on L:\Fs2\Data

Run the front end.

I use the batch file method of assigning the drive letter because sometimes
I hook up to the real server and want to use the same drive letter for other
purposes.

To remove the drive letter assignment you could write another
RemoveLDrive.bat file containing:
subst L: /d
and run it when you want the L: drive to go away.
It will go away when you reboot anyway.

HTH
Mich
 
Mich:
Thank you.
Allan
-----Original Message-----
Here's one way:
Create a folder on your notebook called
c:\Development

Right click on that folder and select Sharing
Shared as should say DEVELOPMENT
So now this folder is shared as DEVELOPMENT

In Notepad, create a new file and place this line in it:
subst L: c:\development
Save the file as LDrive.bat

Create folders under c:\development so that you now have:
c:\development\Fs2\Data

If you look in Explorer and look for an L: drive you should not have one.
Double-click the LDrive.bat file
Now look in Explorer, you will see an L: drive with an Fs2 folder and Data
subfolder.
Put your copy of the backend there, same as on the server.

Put your front end somewhere, it doesn't matter where, as long as it knows
the data is on L:\Fs2\Data

Run the front end.

I use the batch file method of assigning the drive letter because sometimes
I hook up to the real server and want to use the same drive letter for other
purposes.

To remove the drive letter assignment you could write another
RemoveLDrive.bat file containing:
subst L: /d
and run it when you want the L: drive to go away.
It will go away when you reboot anyway.

HTH
Mich




.
Click to expand...
 
Back
Top