I am in the process of converting 5 of my databases (thanks Tom) into Front
and Back Ends when it occurs to me that that since I have to link the Back
Ends in any case, I may be able to do away with duplications of tables in
Back End sections.
Can one Front End look at more then one Back End at the same time and if so
can it cause problems in the future replication or otherwise?Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/13865-i-am-out-of-my-depth.html
All of my databases looks at tables "Countries", "States", "Cites" for
address, dialling & postal codes, local time etc, which in turn looks at
other tables such as "Holidays Rules " (world-wide) and their dates,Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=13865
Daylight Saving (Summer) Time Rules date etc ect etc.
"Countries" and "States" require very little maintenance but the "Cities"
table which in fact a locations table (cities, towns, suburbs, villages and
other locations, world wide) is constantly updated. It has around 19,000
records so far.
I am thinking about a possibility of creating one Back End for those tables
as a separate database whereby each of the other databases' Front Ends will
be able to look at and update it as necessary (the routines for it are
already in most of the databases)
At the moment each database has its own set (almost identical) except world
"Holidays Dates" with is updated by one database, once a year, and is linked
to the rest.
Appreciate your views