Simple ? Splitting Database

[Guest]

I am finally going to start deploying a front end executable for a tool I
built that has been shared on our network.

Question: Once I split the Database, I finalize the front end making sure
the table links are correct. Then I make a copy of the front end, and create
the MDE from the copy, correct?

After that I can make modifications to the front end and then copy again
making the new MDE, right?

But I have to have the links correct before creating the MDE.

Thanks for advice

 

[Rick Brandt]

I am finally going to start deploying a front end executable for a
tool I built that has been shared on our network.

Question: Once I split the Database, I finalize the front end making
sure the table links are correct. Then I make a copy of the front
end, and create the MDE from the copy, correct?

After that I can make modifications to the front end and then copy
again making the new MDE, right?

But I have to have the links correct before creating the MDE.

Thanks for advice

The creation of an MDE always results in a new file, not the conversion of an
existing one so you can just make the MDE directly from your master MDB. Also
you can make and alter tables links in an MDE. You just can't make or alter
*code-based* objects (forms, reports, modules).

 

[Douglas J. Steele]

You could (and probably should) include code in your front-end to allow you
to relink the front-end to the back-end, just in case the back-end moves.

There's a complete example at http://www.mvps.org/access/tables/tbl0009.htm
at "The Access Web"

Other than that, yes, your understanding is correct.

 

[Allen Browne]

Jeff, there are a couple of ways of doing this.

What I do is to run some code on application startup that checks the back
end is available. If not, it pops up the File Open dialog asking the user to
locate it. This handles cases where a server is renamed, or even if the
network is down.

There's a module you can copy and adapt from solutions.mdb, sample database
from Microsoft at:
http://support.microsoft.com/kb/248674/en-us

Tony Toews has another solution here:
http://www.granite.ab.ca/access/autofe.htm
While I don't use his solution, I understand that he uses the equivalent of
an INI file to hold the path name, so the front end connects itself to the
specified path when you start up.

 

[Guest]

Rick, Doug, Allen:

Thanks Guys! Appreciate your help
--
Jeff C
Live Well .. Be Happy In All You Do

Jeff, there are a couple of ways of doing this.

What I do is to run some code on application startup that checks the back
end is available. If not, it pops up the File Open dialog asking the user to
locate it. This handles cases where a server is renamed, or even if the
network is down.

There's a module you can copy and adapt from solutions.mdb, sample database
from Microsoft at:
http://support.microsoft.com/kb/248674/en-us

Tony Toews has another solution here:
http://www.granite.ab.ca/access/autofe.htm
While I don't use his solution, I understand that he uses the equivalent of
an INI file to hold the path name, so the front end connects itself to the
specified path when you start up.