Reload Front End

  • Thread starter Thread starter DS
  • Start date Start date
D

DS

If my Front End on a FE/BE setup goes south and I reload a new Front End do
I need to relink? If so can I do it through code?
Thanks
DS
 
DS said:
If my Front End on a FE/BE setup goes south and I reload a new Front End
do I need to relink? If so can I do it through code?
Thanks
DS
Click to expand...

You'll only need to re-link if the new front end your giving to the person
is not already pointing to the file on your server, or wherever it may be.

In other words if I'm on a client's site, and I have a new version of my
software (a new front end),

What I will do is take the MDB and link to the backend on the server (note
you want to use UNC path name here, DO NOT use mapped drive since that might
be different on each machine ).

once I have the filings, then the next act is converted into a mde for
distribution to the users. at this point since I broke the linked the
database to the back end, then no linking is needed all when this new front
end is placed on each computer.

If you're going to be offsite and you can't be on the client's machine, then
of course you'll have to come up with some type of re-linking scheme that
will remember the previous location to the back end. in fact in my reeling
King code, I actually read of small text filed in the application directory
where the front and resides. On my application start up I test for good link
to the back end, and if it fails, then I read in that text file to get the
location, and then run the re-link code. and if there's no little small text
file, it means that the users never link it to the back end, and then I fire
up the application browse dialogue for the person to browse to the back end.

You can use the code here to re-link.

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

the code to pop open the file browse dialog is here:

http://www.mvps.org/access/api/api0001.htm

Between the above two routines, I think most of those developers have had to
break down and cobble together some type of re-link system to manage the
situation. as mentioned, if you're going to be on site to maintain the
software, then just simply link your file, create the mde, and then
distribute that mde to your users pc's.
 
Thanks Albert, a lot of good info. So since I am replacing the same exact
file with no changes to it I'm assuming that I don't have to relink. Like I
said this is only if the front end breaks for some reason. I set up an
outside database to exchange the old file for the new file.
Thanks
DS
 
Back
Top