Linking and copying question

[Guest]

I have a front end/back end database system (both being mde's). I have code
that will copy the front and back end databases to the same folder and it
works fine. I want to give the user the option to save a backup of the two
database.mde's to a different location. What I am having a problem with is
that I can save them to another folder OK but when I try to open the front
end db the next time I can't get anything to run, the splash screen won't
even appear. Could this be a problem because of the links? Is the original
front end db trying now to link with the copied backend db (which would be in
a different folder)?

Thanks

 

[John Vinson]

I have a front end/back end database system (both being mde's).

There's really no benefit to making a table-only backend a .mde, to my
knowledge. The difference between a .mdb and a .mde is the handling of
vba code (of which there is none in the backend) and in the ability to
go into design mode on forms and reports (likewise).

Don't think it would hurt, but neither is it necessary.

I have code
that will copy the front and back end databases to the same folder and it
works fine. I want to give the user the option to save a backup of the two
database.mde's to a different location. What I am having a problem with is
that I can save them to another folder OK but when I try to open the front
end db the next time I can't get anything to run, the splash screen won't
even appear. Could this be a problem because of the links? Is the original
front end db trying now to link with the copied backend db (which would be in
a different folder)?

It will keep the same path and filename. This is a good reason to
either use a \\server\path\filename type link rather than using mapped
drive names, or to obtain some good "relinking" software such as that
in the Access Developer's Handbook.

John W. Vinson[MVP]