Packaging a Split Dbase

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello all,
Well thank you all for your help with my database, now I need to package
this thing and I'm a little confused.
I would like to package a split MDE database because the BE will be going on
a client's network (I don't know the drive mapping yet) and the FE will be on
a few PCs. I wanted it split because I would like to send updates and
maintain the BE data.
My question is this:
1. After I split the database and convert it to MDE, is the BE going to be
packaged automatically with the FE?
2. How do I map the FE to the BE on the new network that it will be
installed on?
Could someone help me?
 
Thanks Douglas!
What about the packaging part?
Will it only package the FE?
And then how would be the best way to deploy/package the BE for the first
time?
I would think, just include it as an additional file and have someone from
their IT department copy to somewhere on their network but that dosn't seem
very professional on my part.
 
There's no reason to include the BE in the package: all you have to do is
put it in the correct place on the server, whereas each user is going to
have to run the package to ensure the application's properly installed on
their desktop.

If you're really concerned, you could put code in your FE to generate the BE
if it doesn't exist, but that's a bit of overkill.
 
So then before I split it and package it I would need to know the clients
network drives... right?
 
Not necessarily. If you put relinking code in your FE, they can link it
themselves.
 
Back
Top