Backend Frontend Network

[ordy62]

I split a database to a FE and BE but the issue is the network shares.
I have several groups that need to view this database but the network
paths to database are different for example.


Network drive F:\Projects\sha red\database_be .mdb (original location)

Group 2
L:\Department Folder\Projects \shared\databas e_mdb

and the other groups the mapping is different also. They can all open
the FE switchboard but once they try to open a report or form it tells
them that F:\Projects\sha red\database_be .mdb doesn't exist. Any
suggestions?

Thanks
Ordy62

[Bob Alston]

Re: Backend Frontend Network

ordy62 wrote:

I split a database to a FE and BE but the issue is the network shares.
I have several groups that need to view this database but the network
paths to database are different for example.
>
>
Network drive F:\Projects\sha red\database_be .mdb (original location)
>
Group 2
L:\Department Folder\Projects \shared\databas e_mdb
>
and the other groups the mapping is different also. They can all open
the FE switchboard but once they try to open a report or form it tells
them that F:\Projects\sha red\database_be .mdb doesn't exist. Any
suggestions?
>
Thanks
Ordy62
>

Either set common drive mappings to the backend or

use UNC mappings to the backend
ex. \\backendcomput ername\fullyqua lified path

Bob

[ordy62]

Re: Backend Frontend Network

Common mapping won't go MIS has it set differently for each department.
Can you explain UNC mapping for me where do i find it and set it
etc...also someone mention Link Table Manager might fix the issue from
each client with the selection of "always prompt for a new location"
selected. Thanks and Happy New Year!

ordy

Bob Alston wrote:

ordy62 wrote:

I split a database to a FE and BE but the issue is the network shares.
I have several groups that need to view this database but the network
paths to database are different for example.


Network drive F:\Projects\sha red\database_be .mdb (original location)

Group 2
L:\Department Folder\Projects \shared\databas e_mdb

and the other groups the mapping is different also. They can all open
the FE switchboard but once they try to open a report or form it tells
them that F:\Projects\sha red\database_be .mdb doesn't exist. Any
suggestions?

Thanks
Ordy62

Either set common drive mappings to the backend or
>
use UNC mappings to the backend
ex. \\backendcomput ername\fullyqua lified path
>
Bob

[Bob Alston]

Re: Backend Frontend Network

ordy62 wrote:

Common mapping won't go MIS has it set differently for each department.
Can you explain UNC mapping for me where do i find it and set it
etc...also someone mention Link Table Manager might fix the issue from
each client with the selection of "always prompt for a new location"
selected. Thanks and Happy New Year!
>
ordy
>
Bob Alston wrote:

>ordy62 wrote:

>>I split a database to a FE and BE but the issue is the network shares.
>>I have several groups that need to view this database but the network
>>paths to database are different for example.
>>>
>>>
>>Network drive F:\Projects\sha red\database_be .mdb (original location)
>>>
>>Group 2
>>L:\Departme nt Folder\Projects \shared\databas e_mdb
>>>
>>and the other groups the mapping is different also. They can all open
>>the FE switchboard but once they try to open a report or form it tells
>>them that F:\Projects\sha red\database_be .mdb doesn't exist. Any
>>suggestions ?
>>>
>>Thanks
>>Ordy62
>>>

>Either set common drive mappings to the backend or
>>
>use UNC mappings to the backend
>ex. \\backendcomput ername\fullyqua lified path
>>
>Bob

>

When relinking the FE to the BE...

use MY network places, Entire network, Microsoft Windows network, then
select the back end server name, then navigate to the BE database.

do this before you distribute the FE database and you will be all set.

Bob

[John Mishefske]

Re: Backend Frontend Network

ordy62 wrote:

Common mapping won't go MIS has it set differently for each department.
Can you explain UNC mapping for me where do i find it and set it
etc...also someone mention Link Table Manager might fix the issue from
each client with the selection of "always prompt for a new location"
selected. Thanks and Happy New Year!

Check out this link which would allow you to convert from a mapped drive letter to its UNC
equivalent:

http://www.mvps.org/access/api/api0003.htm

--
'---------------
'John Mishefske
'---------------

[ordy62]

Re: Backend Frontend Network

Any idea how to do that with a novell network.
Bob Alston wrote:

ordy62 wrote:

Common mapping won't go MIS has it set differently for each department.
Can you explain UNC mapping for me where do i find it and set it
etc...also someone mention Link Table Manager might fix the issue from
each client with the selection of "always prompt for a new location"
selected. Thanks and Happy New Year!

ordy

Bob Alston wrote:

ordy62 wrote:
>I split a database to a FE and BE but the issue is the network shares.
>I have several groups that need to view this database but the network
>paths to database are different for example.
>>
>>
>Network drive F:\Projects\sha red\database_be .mdb (original location)
>>
>Group 2
>L:\Departmen t Folder\Projects \shared\databas e_mdb
>>
>and the other groups the mapping is different also. They can all open
>the FE switchboard but once they try to open a report or form it tells
>them that F:\Projects\sha red\database_be .mdb doesn't exist. Any
>suggestions?
>>
>Thanks
>Ordy62
>>
Either set common drive mappings to the backend or
>
use UNC mappings to the backend
ex. \\backendcomput ername\fullyqua lified path
>
Bob

When relinking the FE to the BE...
>
use MY network places, Entire network, Microsoft Windows network, then
select the back end server name, then navigate to the BE database.
>
do this before you distribute the FE database and you will be all set.
>
Bob