G
Guest
Hi,
I have a database that I've deployed on our network. After designing it, I
implemented user-level security and then manually split it (see
http://www.jmwild.com/SplitSecure.htm for a description of that).
Unfortunately, my frontend began behaving erratically (it appears corrupted),
so I need to replace it.
The only backup I have is the design database, which was saved previous to
the security implementation and subsequent split. Is there a way to reuse
the existing Secured.MDW file to secure the new frontend, or do I have to
start all over with the secure-and-split process? If I have to start over,
will the new "Secured.MDW" still work with the old backend?
Thanks in advance for your help!
I have a database that I've deployed on our network. After designing it, I
implemented user-level security and then manually split it (see
http://www.jmwild.com/SplitSecure.htm for a description of that).
Unfortunately, my frontend began behaving erratically (it appears corrupted),
so I need to replace it.
The only backup I have is the design database, which was saved previous to
the security implementation and subsequent split. Is there a way to reuse
the existing Secured.MDW file to secure the new frontend, or do I have to
start all over with the secure-and-split process? If I have to start over,
will the new "Secured.MDW" still work with the old backend?
Thanks in advance for your help!