|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
April 20th, 2009, 10:26 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
Spilt DB causes Error "not a valid path"
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  ocuments 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 
|
|
#2
April 20th, 2009, 11:36 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Spilt DB causes Error "not a valid path"
On Mon, 20 Apr 2009 14:26:01 -0700, Heather
wrote: 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 ocuments 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
|
|
#3
April 20th, 2009, 11:38 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Spilt DB causes Error "not a valid path"
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 "Heather" wrote in message ... 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 ocuments and settings\Reporting_be.mdb is not a validpath. It is looking for my C: Drive. Can someone tell me what am I doing wrong? Thanks, Heather
|
|
#4
April 21st, 2009, 01:06 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Spilt DB causes Error "not a valid path"
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? "Jeff Boyce" wrote: 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 "Heather" wrote in message ... 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 ocuments and settings\Reporting_be.mdb is not a validpath. It is looking for my C: Drive. Can someone tell me what am I doing wrong? Thanks, Heather
|
|
#5
April 21st, 2009, 01:19 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Spilt DB causes Error "not a valid path"
On Mon, 20 Apr 2009 17:06:03 -0700, Heather
wrote: 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
|
|
#6
April 21st, 2009, 02:34 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Spilt DB causes Error "not a valid path"
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 "Armen Stein" wrote: On Mon, 20 Apr 2009 17:06:03 -0700, Heather wrote: 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
|
|
#7
April 21st, 2009, 08:13 AM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
Spilt DB causes Error "not a valid path"
On Mon, 20 Apr 2009 18:34:01 -0700, Heather
wrote: 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
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
