main form has back-end table data source

[Mark Kubicki]

i have what i'm certain must be a common issue, and am wondering if there is
a "usual" way of handeling it...

On the main form, that opens when the database is loaded, I have information
(in text boxes and labels...) that comes from a linked back end table. The
problem is that if the table is moved, the links fail and the main form
won't open. (don't ask the circumstances... just know that it is quite
possible that the b/e table could be moved, or renamed, or what have you...
and this is an inherited given and must accomadated)

I thought something like on exting the database I should relink the tables
to the front end database.. naw, that doesn't make any sense... maybe I
should create a splash page that validates the file location and that, if
necessary, gives a way of re-mapping the link!?!?!

This must happen all the time; how do the ecxperts handel it?

any suggestions would be greatly appreciated
thank in advance,
mark

 

[Piet Linden]

i have what i'm certain must be a common issue, and am wondering if thereis
a "usual" way of handeling it...

On the main form, that opens when the database is loaded, I have information
(in text boxes and labels...) that comes from a linked back end table.  The
problem is that if the table is moved, the links fail and the main form
won't open.   (don't ask the circumstances... just know that it is quite
possible that the b/e table could be moved, or renamed, or what have you....
and this is an inherited given and must accomadated)

I thought something like on exting the database I should relink the tables
to the front end database.. naw, that doesn't make any sense... maybe I
should create a splash page that validates the file location and that, if
necessary, gives a way of re-mapping the link!?!?!

This must happen all the time; how do the ecxperts handel it?

any suggestions would be greatly appreciated
thank in advance,
mark

you could use something like this if you test for the backend (using
DIR) and don't find it:
http://www.mvps.org/access/tables/tbl0009.htm

 

[Mark Kubicki]

very (very) helpful... thanks,
-m.

i have what i'm certain must be a common issue, and am wondering if there
is
a "usual" way of handeling it...

On the main form, that opens when the database is loaded, I have
information
(in text boxes and labels...) that comes from a linked back end table. The
problem is that if the table is moved, the links fail and the main form
won't open. (don't ask the circumstances... just know that it is quite
possible that the b/e table could be moved, or renamed, or what have
you...
and this is an inherited given and must accomadated)

I thought something like on exting the database I should relink the tables
to the front end database.. naw, that doesn't make any sense... maybe I
should create a splash page that validates the file location and that, if
necessary, gives a way of re-mapping the link!?!?!

This must happen all the time; how do the ecxperts handel it?

any suggestions would be greatly appreciated
thank in advance,
mark

you could use something like this if you test for the backend (using
DIR) and don't find it:
http://www.mvps.org/access/tables/tbl0009.htm

 

[Piet Linden]

very (very) helpful... thanks,
-m.








you could use something like this if you test for the backend (using
DIR) and don't find it:http://www.mvps.org/access/tables/tbl0009.htm

something like this will work:

Private Sub cmdTestDir_Click()
Dim strNewFile As String

If Dir(Me.txtFileToImport) = "" Then
MsgBox "Could not find the file!", vbOKOnly + vbInformation +
vbCritical
strNewFile = GetOpenFile("C:\", "Navigate to the backend
file...")
Else
MsgBox "your file is here: " & Me.txtFileToImport
End If
End Sub

the GetOpenFile stuff is here:
http://www.mvps.org/access/api/api0001.htm