Splitting Database

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

Guest

When I split a database, does the front end need to backed up with the same
frequency as the back end,or does only the back end need to be backed up?

To put a copy of the front end on another users machine. Can I just cut and
paste a copy from a public folder on the network from the users machine? Or
is it better to copy it from my machine to a removable disk and then copy to
the users machine?
 
Since the front-end will not change (unless you release a new version),
there is no need to back it up regularly.

How to get it on their PC does not really matter. I used to keep a copy on
the LAN and I stored a field value (version) in a table on the front-end,
and a "current version" in a table on the front end. When the user would
open the database, it would compare these two values. If they did not
match, it would erase their front-end from their hard drive, and copy down
the newer version from the shared drive. This made the update process
automatic. Each time I put a new version out there, I'd create a backup
copy.
 
of course; if you used Access Data Projects; it would be a lot easier
to manage. You woudln't have a performance penalty for running stuff
across the network. And performance? Reliability?

ADP wins every competition against MDB.

-Aaron
ADP Nationalist
 
of course; if you used Access Data Projects; it would be a lot easier
to manage. You woudln't have a performance penalty for running stuff
across the network. And performance? Reliability?

ADP wins every competition against MDB.

-Aaron
ADP Nationalist
Click to expand...

Time to get back on your meds. :-)
 
JoeA2006 said:
When I split a database, does the front end need to backed up with
the same frequency as the back end,or does only the back end need to
be backed up?

To put a copy of the front end on another users machine. Can I just
cut and paste a copy from a public folder on the network from the
users machine? Or is it better to copy it from my machine to a
removable disk and then copy to the users machine?
Click to expand...

There are some applications when the front end may contain a dynamic
table(s). That is one or more tables that contain information that might
apply only to that front end and may change based on the needs of that user.
Those front ends should be backed up anytime there is a change in that
table. If you have no dynamic tables, then there would no reason to back it
up at any time other than when there are changes to the front end design.
 
In which case they should have locally linked tables for that data, due to
the upgrade <g>

Pieter
 
this 'dynamic table' crap that you talk about?

you can conceptualize this as a permanent table with a filter where
SPID = @@SPID.

wrap this into a view-- and you've got your multi-user dynamic table.

it's a much more elegant solution than keeping your data in a dozen
different databases.
 
Back
Top