Splitting a Database

[Sondra]

I've read all the messages about splitting a database and i have actually
completed the task; however, I have this major issue.

Our company works out of 3 different states. The database is currently
housed on a shared server, but 2 out of 3 states have different drive id's
for the server; i.e., Idaho and Montana (I:/Drive) and Utah (R:/Drive).

The split works great for the Idaho and Montana staff but the Utah staff
gets the message that the files can't be found. It's looking for them on the
I:/Drive. Is there anyway to get around this problem?

thanks in Advance

 

[dhstein]

Sondra,

If Utah doesn't use the "I" drive already , then you have 2 choices

1) Map I to the appropriate location.

2) Use the DOS command to substitute a drive

SUBST I: R:\Drive

You'll have to set up a login script or some automated way to keep the drive
after a reboot. One simple approach is to create a .BAT (IDRIVE.BAT for
example) file - put it in a folder like C:\BATCH. Then run that script from
your startup folder on the user's systems.

 

[John Spencer]

OR set up the link using a UNC path.

If you don't know what that is talk to your network folks.

Basic Steps (Access 2003 and Windows XP)
-- Tools: Database Tools: Linked Table Manager from menu
-- Select All button
-- Check Always Prompt for new Location
-- Click OK
-- Double Click on My Network Places
-- Double Click on Entire Network
-- Find the Server where the backend database is located
-- Navigate to the backend database
-- Double Click on the backend database to set up linkage using UNC.

'====================================================
John Spencer
Access MVP 2002-2005, 2007-2009
The Hilltop Institute
University of Maryland Baltimore County
'====================================================

 

[John W. Vinson]

I've read all the messages about splitting a database and i have actually
completed the task; however, I have this major issue.

Our company works out of 3 different states. The database is currently
housed on a shared server, but 2 out of 3 states have different drive id's
for the server; i.e., Idaho and Montana (I:/Drive) and Utah (R:/Drive).

The split works great for the Idaho and Montana staff but the Utah staff
gets the message that the files can't be found. It's looking for them on the
I:/Drive. Is there anyway to get around this problem?

thanks in Advance

If you're trying to use a wide-area network or the Internet to connect a
frontend in Montana to a backend in Utah... *YOU'RE IN FOR TROUBLE*.

Access is NOT designed and not suitable for that purpose. You should really
consider storing the backend (the data) in SQL/Server or another client/server
database, and carefully designing the frontend to deal with the connectivity
and performance issues of a wide-area connection.

 

[aaron.kempf]

Access DAta Projects are the only way to do this.

Linked tables cannot ever run across any network. (wireless, wan,
vpn, etc)

-Aaron

 

[Sondra]

John:

I'm going to give this a try. If I understand the instructions you gave, I
shouldn't have any other issues with the way it is identified.

Thanks...I'll keep you informed.

 

[Tony Toews [MVP]]

Access DAta Projects are the only way to do this.

Linked tables cannot ever run across any network. (wireless, wan,
vpn, etc)

This is totally wrong.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[aaron.kempf]

LINKED TABLES CANNOT RUN ACROSS ANY NETWORK
WAN, WIRELESS, VPN, ETC

PLEASE, OH GREAT CANADIAN BACON-- PLEASE EXPLAIN TO ME HOW I AM
WRONG??

JET FUCKING SUCKS AND A GOOD 50% OF THE REASON IS BECAUSE IT DOESN'T
WORK ACROSS (MOST) NETWORKS

-Aaron