Relink tables questions

[BruceM]

I am getting ready to deploy a split database. I know there is code at the
MVP web site to relink tables at startup, but I don't understand the
circumstances that would make relinking necessary. I have read newsgroup
postings on the subject of the relinking code. In my project the linked
tables are from two databases. As I understand it, the code would need to
be revised before it will work properly in a multiple-backend situation.
Before I embark on that journey, how important is it to relink the tables at
startup. The linked tables are in network locations that are not likely to
change. If they do, I can issue new FE files.

If the tables do not link properly, I most certainly *do not* wish to
present users with a dialog for selecting the correct database file. I
suppose I would need to replace the dialog with an error message about
notifying an administrator.

 

[Klatuu]

Relinking at startup is not an absolute necessity; however, looping through
the tables and refreshing the links is not a bad idea. There are many things
that can happen that would cause your application problems if the back end is
not available. For example, the network is down, a network admin changed the
name of a folder, etc. Refreshing the links would let you know immediately
if a problem exists.

I don't understand your reluctance to allow users to relink to the database.
If properly handled, this can save you some grief and keep your users
working and somewhat happier when you are not available to fix the problem.

 

[Allen Browne]

You do need to check that the data is available at startup, and take some
action if not - even if that's just to close gracefully.

Relinking is simple enough: set the Connect property and RefreshLink. It may
be necessary if a server is out, and you need to link to a different server
or path.

If you are on-site and can issue a new front-end with the right links,
that's fine.

 

[Mr. B]

I am getting ready to deploy a split database. I know there is code at the
MVP web site to relink tables at startup, but I don't understand the
circumstances that would make relinking necessary. I have read newsgroup
postings on the subject of the relinking code. In my project the linked
tables are from two databases. As I understand it, the code would need to
be revised before it will work properly in a multiple-backend situation.
Before I embark on that journey, how important is it to relink the tables at
startup. The linked tables are in network locations that are not likely to
change. If they do, I can issue new FE files.

If the tables do not link properly, I most certainly *do not* wish to
present users with a dialog for selecting the correct database file. I
suppose I would need to replace the dialog with an error message about
notifying an administrator.

Bruce,

In a perfect world you would most likely not ever have to worry about
relinking your tables. However, with that said, we do not live in that
perfect world. Files get moved (no one ever know why), they even get
deleted :>(, they get renamed (same problem - must relink), and event
the network will go down and not be available. So, in short, there
are multiple reasons for building in an attempt to relink to your
backend files.

Then, if you like, you can take the appropriate action when the files
are not found.

HTH

Mr B

 

[BruceM]

My reluctance at having the users relink is that while the database will be
used widely, most users will not use it often. I can't expect an occasional
user to remember the locations of the BE files. You said the key words:
"If properly handled."
However, your comments, and those of others who answered in this thread, are
the sort of feedback for which I was hoping. The message is clear that
refreshing the links is a sound practice.

 

[Mr. B]

My reluctance at having the users relink is that while the database will be
used widely, most users will not use it often. I can't expect an occasional
user to remember the locations of the BE files. You said the key words:
"If properly handled."
However, your comments, and those of others who answered in this thread, are
the sort of feedback for which I was hoping. The message is clear that
refreshing the links is a sound practice.








- Show quoted text -

Bruce,

Keep in mind that "relinking" is simply a process for making sure that
the data can be found. It should not require your users to remember
where the backend data file is or what it is named.

If your code returns an error, you know that the data file is not
available and you can inform the user or just exit with some kind of
message for your users.

Mr B

 

[BruceM]

That's what I was thinking: to have them contact somebody who can
straighten it out.

 

[Marshall Barton]

I am getting ready to deploy a split database. I know there is code at the
MVP web site to relink tables at startup, but I don't understand the
circumstances that would make relinking necessary. I have read newsgroup
postings on the subject of the relinking code. In my project the linked
tables are from two databases. As I understand it, the code would need to
be revised before it will work properly in a multiple-backend situation.
Before I embark on that journey, how important is it to relink the tables at
startup. The linked tables are in network locations that are not likely to
change. If they do, I can issue new FE files.

If the tables do not link properly, I most certainly *do not* wish to
present users with a dialog for selecting the correct database file. I
suppose I would need to replace the dialog with an error message about
notifying an administrator.

As others have said, relinking is not normally needed.

BUT, as I recently discovered, if you have to change
somethng in a back end table, you should at least Compact
every copy of the front end file to force all queries to
reconstruct their cached tables information. Since this may
not be convenient, relinking should be a viable alternative.

 

[Mr. B]

As others have said, relinking is not normally needed.

BUT, as I recently discovered, if you have to change
somethng in a back end table, you should at least Compact
every copy of the front end file to force all queries to
reconstruct their cached tables information. Since this may
not be convenient, relinking should be a viable alternative.

Bruce,

Yes,as you have just pointed out, if you provide the code that attempt
to refresh the links, then at least if it fails, your user will get
some idea as to what is going on and can then contact someone else.

Mr. B

 

[BruceM]

This is where the forum is so valuable. You have a lot of experience with
Access, yet just recently you discovered something rather important, and are
now passing that along. Thanks for the insight.