By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,504 Members | 1,212 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,504 IT Pros & Developers. It's quick & easy.

Security - FE BE - Replication

P: n/a
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?
Gerald

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200607/1
Jul 18 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Anyone?

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?

Gerald
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200607/1
Jul 21 '06 #2

P: n/a
"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/
Jul 21 '06 #3

P: n/a
Thanks for the response David. I understand about the backup situation. I
guess I did not make myself complete clear.
What do I need to do first?
Split?
Secure?
Replicate?

Is this the order I need to follow?
David W. Fenton wrote:
>>>I am nearing the end of my development for my application. Here is
my scenario.
[quoted text clipped - 13 lines]
>>
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.
--
Message posted via http://www.accessmonster.com
Jul 22 '06 #4

P: n/a
"gjameson via AccessMonster.com" <u21717@uwewrote in
news:63a1d825ec77d@uwe:
Thanks for the response David. I understand about the backup
situation. I guess I did not make myself complete clear.
What do I need to do first?
Split?
Secure?
Replicate?

Is this the order I need to follow?
I think that order works, as my first major replicated app was fully
secured, and it wasn't replicated until after it was already in
production use. I'm not sure it matters which order you do the first
two steps in, but, obviously, you have to split before replicating.

I assume you understand that only the back end (data tables) should
be replicated.

Also, the best newsgroup for replication is
microsoft.public.access.replication.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Jul 22 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.