Single Front End with split back ends

[Simon Webb]

My application contains a lot of rules defined logic, the logic being held
in tables.

It makes sense for me to keep the rules tables in a seperate mdb from the
actual data. I am hoping that during the life of the system any upgrades
will result in changes to the rules tables rather than changes to the data.
This means that - hopefully - the majority of changes will just suppling
new front ends / rules mdb rather than having to amend the data mdb on a
live installation.

Are there any known issues on a front end being linked to two or more back
ends?

thanks in advance

Simon

 

[Douglas J. Steele]

I've never heard of any issues with having multiple back ends.

 

[Albert D. Kallal]

I don't see any particular problem with having two back ends.

However, why not put those tables in the font end? This will make your
updates to users MUCH easer, as then for the next great version, you only
have to send out a new mde front end to the users....

If you make a separate back end table for this config type data, then your
deployment becomes much more complex, as then you can't just email or copy
the front end to each users machine...

I have a number of config types tables in my applications, and I place them
in the front end, and thus re-deployment is far easier. In fact, I use the
free "inno" installer. Here is a set of screen shots as how my ms-access
software is updated:

http://www.kallal.ca/ridestutorialp/upgrade.html

So, you can have two back end tables, but why not just put the tables in the
front end, and then eliminate that extra complexity of having to link to two
back end mdb files?

My re-link code saves the path name to the back end in a text file in the
same dir as the mde on the users machine. Hence, when they upgrade, I only
have to email (or place on a web site) the new mde for them to download. The
re-link code checks this text file..and re-links to the back end. So, don't
even have to know, or care where the back end. (as mentioned, I wrap that
mde in a inno install, so users just have to click on it to install).

I mean, you always update a copy of the mde on each machine...right?
Updating one file on the users pc is less complex then updating both a file
on the pc, and then also figuring out where the new config mdb has to be
placed for the back end - that is bit complex.

 

[Guest]

You can't apply declarative relational integrity rules between two files.

You need to keep links open to both files.

The relink wizard relinks one table at a time if you select tables from both
files.

(david)