Manually changing a linked table location

[Gerry Abbott]

I deploy be-fe solutions to clients, and provide them with updates as a web
link to the Fe file, wrapped in an installer.
I can generally simulate their shares, if they are using a mapped drive.

However if they are not using mapped drives, and are using their own domain
server address, then I cannot simulate that so easy.

Can i manually change the address where the linked table objects point,
before deployment.?
(I cant do it with a relink, since the location i want to provide the link
for is not on my network, and having to get the client to do the relink
defeats the objective of providing a simple update solution)

I noted that the current link address is stored in the mSysObjects table,
but it appears not to be adjustable.

Thanks in advance.

Gerry Abbott,

[Allen Browne]

AFAIK, Gerry, there is no way to set the link to a non-existient location.

There are various ways to simulate it, but the simplest approach is probably
to test the existence of the back end on startup, and if not found, ask the
user to locate the file. There's an example of how to do that in the module
of solutions.mdb:
http://msdn.microsoft.com/library/of...dbdownload.htm

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Gerry Abbott" <pl****@ask.ie> wrote in message
news:a0*****************@news.indigo.ie...

I deploy be-fe solutions to clients, and provide them with updates as a web
link to the Fe file, wrapped in an installer.
I can generally simulate their shares, if they are using a mapped drive.

However if they are not using mapped drives, and are using their own
domain server address, then I cannot simulate that so easy.

Can i manually change the address where the linked table objects point,
before deployment.?
(I cant do it with a relink, since the location i want to provide the link
for is not on my network, and having to get the client to do the relink
defeats the objective of providing a simple update solution)

I noted that the current link address is stored in the mSysObjects table,
but it appears not to be adjustable.

Thanks in advance.

Gerry Abbott

[Gerry Abbott]

Thanks for the prompt reply, Allen,
Ive used the re-link code in other apps, but its still less than eloquent
especially if there several fe users to install for.
However, since that code uses the windows comdlg32.dll to get the file
location and name, i could replace that with
a 'known' file location and name. It could be hard coded, or held in a Fe
local table (that way I could modify it, if the be had to be moved)
This should eliminate user intervention after install. Would you see any
difficulties with this approach.
Gerry Abbott

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:43***********************@per-qv1-newsreader-01.iinet.net.au...

AFAIK, Gerry, there is no way to set the link to a non-existient location.

There are various ways to simulate it, but the simplest approach is
probably to test the existence of the back end on startup, and if not
found, ask the user to locate the file. There's an example of how to do
that in the module of solutions.mdb:
http://msdn.microsoft.com/library/of...dbdownload.htm

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Gerry Abbott" <pl****@ask.ie> wrote in message
news:a0*****************@news.indigo.ie...

I deploy be-fe solutions to clients, and provide them with updates as a
web link to the Fe file, wrapped in an installer.
I can generally simulate their shares, if they are using a mapped drive.

However if they are not using mapped drives, and are using their own
domain server address, then I cannot simulate that so easy.

Can i manually change the address where the linked table objects point,
before deployment.?
(I cant do it with a relink, since the location i want to provide the
link for is not on my network, and having to get the client to do the
relink defeats the objective of providing a simple update solution)

I noted that the current link address is stored in the mSysObjects table,
but it appears not to be adjustable.

Thanks in advance.

Gerry Abbott

[Allen Browne]

No, that's fine.

If you know ahead of time the path that it needs to connect to, and the
fully qualified file name is valid, the code that sets the Connect property
of the TableDef will run fine with no need to call the FileOpen dialog.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Gerry Abbott" <pl****@ask.ie> wrote in message
news:GG****************@news.indigo.ie...

Thanks for the prompt reply, Allen,
Ive used the re-link code in other apps, but its still less than eloquent
especially if there several fe users to install for.
However, since that code uses the windows comdlg32.dll to get the file
location and name, i could replace that with
a 'known' file location and name. It could be hard coded, or held in a Fe
local table (that way I could modify it, if the be had to be moved)
This should eliminate user intervention after install. Would you see any
difficulties with this approach.
Gerry Abbott

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:43***********************@per-qv1-newsreader-01.iinet.net.au...

AFAIK, Gerry, there is no way to set the link to a non-existient
location.

There are various ways to simulate it, but the simplest approach is
probably to test the existence of the back end on startup, and if not
found, ask the user to locate the file. There's an example of how to do
that in the module of solutions.mdb:
http://msdn.microsoft.com/library/of...dbdownload.htm

"Gerry Abbott" <pl****@ask.ie> wrote in message
news:a0*****************@news.indigo.ie...

I deploy be-fe solutions to clients, and provide them with updates as a
web link to the Fe file, wrapped in an installer.
I can generally simulate their shares, if they are using a mapped drive.

However if they are not using mapped drives, and are using their own
domain server address, then I cannot simulate that so easy.

Can i manually change the address where the linked table objects point,
before deployment.?
(I cant do it with a relink, since the location i want to provide the
link for is not on my network, and having to get the client to do the
relink defeats the objective of providing a simple update solution)

I noted that the current link address is stored in the mSysObjects
table, but it appears not to be adjustable.