By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,027 Members | 1,261 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,027 IT Pros & Developers. It's quick & easy.

Reconnecting Front to Back end in Developer

P: n/a
Thank you for your assistance in advance. I'm trying to figure out why on my
computer the front and back ends are ok, when I use Access developer and set up
the program with the front and back ends in the same install folder, I get
errors and no way to reconnect the front and back end on the foreign computer.
Is there something in the developer package that allows this to happen, that
I'm not loading with the program and setup files?

Michael
Nov 12 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
Lumpierbritches wrote:
Thank you for your assistance in advance. I'm trying to figure out
why on my computer the front and back ends are ok, when I use Access
developer and set up the program with the front and back ends in the
same install folder, I get errors and no way to reconnect the front
and back end on the foreign computer. Is there something in the
developer package that allows this to happen, that I'm not loading
with the program and setup files?

Michael


You will need to use the Linked Table Manager add-in to relink your
tables or write/get some code that will refresh the links. The link
stores the physcial logation of the file (eg. C:\database\mydata.mdb).
When moving the data file to the server the link information needs to be
changed to reflect the new location.
--
regards,

Bradley
Nov 12 '05 #2

P: n/a
Thank you, I'm aware that it's stored, but when you compile and use developer,
the link manager isn't part of the develpment package, that I'm aware of, so
how do you relink on the foreign machine?

Michael
Nov 12 '05 #3

P: n/a
In the Setup (developer), there is NO linked table manager. That resides within
Access, as far as I can see.

Michael
Nov 12 '05 #4

P: n/a
Well, I am sure that you know any good developer will provide some code that
handles this linking problem.?

Surely you can't expect your users to use, and have to learn about the
linked table manager?
(how much pain are you trying to inflict on your users?. Perhaps you don't
like them very much!! ;-) )

And, as you rightly point out that the runtime does NOT include the linked
table manager anyway!

If you have reached the point of wanting to distribute your application,
then I am sure that a long time ago you hid the ms-access interface. And,
thus since you long ago hid the ms-access interface..then how have your
provided your users with a means to re-link in the past?

Most developers have simply lifted the code that re-links table from here:

http://www.mvps.org/access/tables/tbl0009.htm

The code to launch up the standard windows file dialog can be found here:

http://www.mvps.org/access/api/index.html

With all of the above hard code written...after an hour or so you can cobble
together a nice routine that allows your users to re-link. In fact, if the
back end table is in the same dir at the front end...then why no attempt a
re-link in your code to the same dir first? This way, if a user moves the
front end, and back end to a different dir..you will not even prompt the
user...and the user will never even know that re-linking had to happen!

Setting up some routines to handling re-linking scenarios is something that
everyone should incorporate into their applications. I even have a re-link
option that I can set before I send the file to a user (when it starts..it
will re-link to the specified dir).

Anyway..the above code is free for the taking..and you can easily use it to
come up with a solution that fits your needs. Doing this will save tons of
support calls. And, any support call that requires your users to re-link
will also be very easy. You can make a re-link button in your custom
menus...(you are using custom menus...right??).

By the time you get around to developing a polished application for
distribution with the runtime..you will have likely had your own re-linking
code running for years.
--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
pl******************@msn.com
http://www.attcanada.net/~kallal.msn
Nov 12 '05 #5

P: n/a
Create a button with this code on click behind it and see if it activates
the linked table manager?

Call Application.Run("acwztool.att_Entry")

"Lumpierbritches" <lu*************@aol.com> wrote in message
news:20***************************@mb-m11.aol.com...
In the Setup (developer), there is NO linked table manager. That resides within Access, as far as I can see.

Michael

Nov 12 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.