Relative table link to a different directory

[Matt]

Hi All,

I have found a version of my answer on GG, but I have not been able to
find my exact answer, thus the post.

I am using Access 2000

Situation:
I have a multi user frontend database located at 'O:\FE.MDB'. This
database contains tables linked to the backend 'M:\BE.MDB' (names have
been changed to protect the innocent). These tables were linked via
the Linked Table Manager and were created using an absolute path
(using the drive letter).

I want to be able to link to the tables using the server name rather
than the drive letter.

What I have = "M:\BE.MDB"
What I want = "\\Server\root\ BE.MDB"

Keep in mind that the frontend resides on an entirely different server
that the backend (all of the solutions I have come across require the
frontend and backend to be in the same folder).
Is this even possible?

[tina]

unless you need to link the tables dynamically at runtime, it's easy enough
to do this manually - once, before distributing the FE to your users -
without using any code, etc. suggest you open the FE and delete all linked
tables, then compact the db. then from the menu bar choose File | Get
External Data | Link Tables. when the link dialog comes up, navigate to the
BE.mdb through Network Neighborhood (or My Network Places, or whatever it's
called on your PC) rather than through the mapped drive letter route. follow
through the rest of the dialog to choose the tables to link, etc, and you're
done.

and if you haven't already, distribute the FE database to each user - don't
allow all your users to open the same, single FE database regardless of
where it's housed.

hth
"Matt" <md*******@yaho o.comwrote in message
news:11******** *************@l 70g2000hse.goog legroups.com...

Hi All,

I have found a version of my answer on GG, but I have not been able to
find my exact answer, thus the post.

I am using Access 2000

Situation:
I have a multi user frontend database located at 'O:\FE.MDB'. This
database contains tables linked to the backend 'M:\BE.MDB' (names have
been changed to protect the innocent). These tables were linked via
the Linked Table Manager and were created using an absolute path
(using the drive letter).

I want to be able to link to the tables using the server name rather
than the drive letter.

What I have = "M:\BE.MDB"
What I want = "\\Server\root\ BE.MDB"

Keep in mind that the frontend resides on an entirely different server
that the backend (all of the solutions I have come across require the
frontend and backend to be in the same folder).
Is this even possible?

[cjakeman]

Hi Tina,

On Aug 2, 4:26 am, "tina" <nos...@address .comwrote:

and if you haven't already, distribute the FE database to each user - don't
allow all your users to open the same, single FE database regardless of
where it's housed.

This is new to me. What goes wrong if users share access to a common
front end database on a network drive?

Thanks,

Chris

[tina]

see http://www.granite.ab.ca/access/splitapp/index.htm.

hth
"cjakeman" <cj******@bigfo ot.comwrote in message
news:11******** **************@ r34g2000hsd.goo glegroups.com.. .

Hi Tina,

On Aug 2, 4:26 am, "tina" <nos...@address .comwrote:

and if you haven't already, distribute the FE database to each user -

don't

allow all your users to open the same, single FE database regardless of
where it's housed.

This is new to me. What goes wrong if users share access to a common
front end database on a network drive?

Thanks,

Chris

[Matt]

On Aug 2, 9:40 am, "tina" <nos...@address .comwrote:

seehttp://www.granite.ab. ca/access/splitapp/index.htm.

hth

"cjakeman" <cjake...@bigfo ot.comwrote in message

news:11******** **************@ r34g2000hsd.goo glegroups.com.. .

Hi Tina,

On Aug 2, 4:26 am, "tina" <nos...@address .comwrote:

and if you haven't already, distribute the FE database to each user -

don't

allow all your users to open the same, single FE database regardless of
where it's housed.

This is new to me. What goes wrong if users share access to a common
front end database on a network drive?

Thanks,

Chris- Hide quoted text -

- Show quoted text -

Thank you ... I actually found some code to do this on GG after some
more searching.

Tina - It is opened through a .BAT file that copies it to the users
local machine each time they open it.

[cjakeman]

On Aug 2, 2:40 pm, "tina" <nos...@address .comwrote:

seehttp://www.granite.ab. ca/access/splitapp/index.htm.

Thanks for the link, but it does answer the question I was trying to
ask. Your link is about splitting a database into front end and back
end and I agree that this has lots of advantages for maintenance etc..

But you also recommended

"distribute the FE database to each user - don't allow all your users to open the same, single FE database regardless of
where it's housed.

Why did you say this? What problems arise if multiple users share a
single front-end MDB file on a shared drive rather than have local
copies?

Thanks,
Chris

[tina]

see http://www.members.shaw.ca/AlbertKal...plit/index.htm

hth
"cjakeman" <cj******@bigfo ot.comwrote in message
news:11******** *************@o 61g2000hsh.goog legroups.com...

On Aug 2, 2:40 pm, "tina" <nos...@address .comwrote:

seehttp://www.granite.ab. ca/access/splitapp/index.htm.

Thanks for the link, but it does answer the question I was trying to
ask. Your link is about splitting a database into front end and back
end and I agree that this has lots of advantages for maintenance etc..

But you also recommended

"distribute the FE database to each user - don't allow all your users

to open the same, single FE database regardless of

where it's housed.

Why did you say this? What problems arise if multiple users share a
single front-end MDB file on a shared drive rather than have local
copies?

Thanks,
Chris