Spilt DB causes Error "not a valid path"

  • Thread starter Thread starter Heather
  • Start date Start date
H

Heather

Hello,

I "Split" a 2003 Access Database with the BE table and FE all the rest
linking to the table in the BE "I used the Access Splitter wizard".
I did the split on my C: Drive of course works good for me because I am the
admin. I then put both MDB Files on a shared folder on the company Network
drive. When a user pulls the FE onto thier desktop they get the following
error message: "C:Documents and settings\Reporting_be.mdb is not a valid
path. It is looking for my C: Drive.

Can someone tell me what am I doing wrong?

Thanks,
Heather
 
Hello,

I "Split" a 2003 Access Database with the BE table and FE all the rest
linking to the table in the BE "I used the Access Splitter wizard".
I did the split on my C: Drive of course works good for me because I am the
admin. I then put both MDB Files on a shared folder on the company Network
drive. When a user pulls the FE onto thier desktop they get the following
error message: "C:Documents and settings\Reporting_be.mdb is not a valid
path. It is looking for my C: Drive.

Can someone tell me what am I doing wrong?

Thanks,
Heather

Hi Heather,

Link the tables *after* you put the MDB files on the server. Use the
full UNC path (starting with \\) so that the path is universal. Then
when each user gets a copy of the front-end, it will already be
linked.

If you want a more automated approach to relinking tables, you're
welcome to use our free J Street Access Relinker at:
http://www.jstreettech.com/downloads

Armen Stein
Microsoft Access MVP
www.JStreetTech.com
 
Heather

You used the wizard ...<g>

The front-end you ended up with is pointed at the back-end you ended up with
ON YOUR PC.

When you moved both to the network, then had folks download the front-end to
their PC, their PC does not have the same directory structure that yours
does. Moreover, the back-end you want them to point to IS NOT the one
(?still?) on your PC. They should be pointing to the one on the network.

Open the front-end you put on the network. Use the Linked Table manager to
re-connect to the back-end tables ON THE NETWORK. Then try downloading a
copy of that front-end to your PC and make sure it runs before turning the
users loose on it.

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP
 
So I split and then I linked the tables once I put the FE & BE on the shared
drive.

But What happens if people map thier drives different then me? So while it
is shared I am mapped as "N" example N:\Platform\Report Database other users
might be P:\Platform\Report Database or L:\Platform\Report Database.

Sorry but how do I really make it generic?
 
But What happens if people map thier drives different then me? So while it
is shared I am mapped as "N" example N:\Platform\Report Database other users
might be P:\Platform\Report Database or L:\Platform\Report Database.

Sorry but how do I really make it generic?

Hi Heather,

Read my other post - that's why it's important to use the UNC path, as
in \\MyServer\MyShare\MyFolder\MyData.mdb.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com
 
It is not allowing me to change the Path in the linked table (open in design
view the table, properties edit description). My DB is split go to front end
- to the linked table and that reads N:\Platform\Report Database and I would
like to change that to your suggestion which is \\fs1051\Platform\Report
Database\ReportTracker_BE.mdb
 
It is not allowing me to change the Path in the linked table (open in design
view the table, properties edit description). My DB is split go to front end
- to the linked table and that reads N:\Platform\Report Database and I would
like to change that to your suggestion which is \\fs1051\Platform\Report
Database\ReportTracker_BE.mdb

Hi Heather,

You don't specify it there - you need to use the Linked Table Manager
and navigate to the UNC path there instead. You can start with
\\fs1051 and navigate from there.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com
 
Back
Top