"gjameson via AccessMonster.com" <u21717@uwewrote in
news:6397b70c446bb@uwe:
gjameson wrote:
>>I am nearing the end of my development for my application. Here is
my scenario.
A few users will use this on the lan. ---- FE BE ----Security
A few users will use this out in the field and come in and sync
the db. (am & pm) ----- Replication------Security
I know I need to split FE BE and do replication and need
security, also do a
backup somewhere.
What do I do first?
Can this all be done?
Anyone?
I'm not certain I understand the question. Can *what* be done? Yes,
of course you can use replication with secured databases. It's a bit
harder, but no harder than using security in non-replicated
databases.
On the backup, you have to remember that with replication, backups
are not quite so simple. If you restore from a backup, you have to
be sure you restore to the original location, but you've also got to
be careful you don't overwrite (and lose) the existing file of the
same name in the same location. Well, unless, of course, that file
is corrupt and you don't want to keep it. In that case I'd rename
it.
But the best way to do backups in replicated apps is to use
REPLICATION. Create one or more backup replicas and synch with them
each time the user closes the front end. That way you can never lose
much data should an edited replica get corrupted.
--
David W. Fenton
http://www.dfenton.com/
usenet at dfenton dot com
http://www.dfenton.com/DFA/ 
