Split Db MDE Question ?

[Gulf Coast Electric]

If I split the db into two parts, front end and back. Then make the front
end a mde, while retaining an original copy of the front end, mdb, Can I
then make changes to the front end original and re-make it into a mde and
send to user without them having to re-link or anything as long as the files
were both kept in the same folder?

--
-------------------------------------------------------------------------
This email and any files transmitted with it from Gulf Coast Electric are
confidential and intended solely for the
use of the individual or entity to which they are addressed.
If you have received this email in error please notify the
sender.
All Mail is pre-scanned with Norton Antivirus 2004 for your protection.
FIGHT BACK AGAINST SPAM!

http://mail.giantcompany.com

 

[Rick Brandt]

If I split the db into two parts, front end and back. Then make the front
end a mde, while retaining an original copy of the front end, mdb, Can I
then make changes to the front end original and re-make it into a mde and
send to user without them having to re-link or anything as long as the files
were both kept in the same folder?

That's the standard drill, yes.

 

[Jim/Chris]

I always keep a copy of the MDB for development linked to a
copy of the backend DB located on my hard drive. At the
time to distribute I make a copy and use the Linked Table
Manager to relink to the production Back End. I then
create the MDE and distribute.

Jim

 

[Douglas J. Steele]

As the others have said, it should work. However, if you're worried, put
your own code in to allow the tables to be relinked. Check
http://www.mvps.org/access/tables/tbl0009.htm at "The Access Web" for one
approach.