I have an Access 2000 db that is secured. I just splitted
it. The Front end is still secured, but that back end is
not. If someone were to go to the the backend folder on
the network, they could delete data. How do I secure the
backend with the same Secured.mdw that is used on the
front end?

Hi, Steve.

> I have an Access 2000 db that is secured. I just splitted
> it. The Front end is still secured, but that back end is
> not.

That's the problem with using the Database Splitter Wizard. It completely
ignores security.

To split it properly, one needs to make an extra copy of the unsplit
database and store that copy where the back end should be. Then, one should
delete all objects in this back end copy, except the tables and
relationships. Next, in the original database, the front end, the tables
should be deleted and new links created to the tables in the back end.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)


"Steve" <(E-Mail Removed)> wrote in message
news:260d01c49f48$3a468ba0$(E-Mail Removed)...
> I have an Access 2000 db that is secured. I just splitted
> it. The Front end is still secured, but that back end is
> not. If someone were to go to the the backend folder on
> the network, they could delete data. How do I secure the
> backend with the same Secured.mdw that is used on the
> front end?
>

Excellent. Thanks.
>-----Original Message-----
>Hi, Steve.
>
>> I have an Access 2000 db that is secured. I just
splitted
>> it. The Front end is still secured, but that back end
is
>> not.
>
>That's the problem with using the Database Splitter
Wizard. It completely
>ignores security.
>
>To split it properly, one needs to make an extra copy of
the unsplit
>database and store that copy where the back end should
be. Then, one should
>delete all objects in this back end copy, except the
tables and
>relationships. Next, in the original database, the front
end, the tables
>should be deleted and new links created to the tables in
the back end.
>
>HTH.
>
>Gunny
>
>See http://www.QBuilt.com for all your database needs.
>See http://www.Access.QBuilt.com for Microsoft Access
tips.
>
>(Please remove ZERO_SPAM from my reply E-mail address, so
that a message
>will be forwarded to me.)
>
>
>"Steve" <(E-Mail Removed)> wrote in
message
>news:260d01c49f48$3a468ba0$(E-Mail Removed)...
>> I have an Access 2000 db that is secured. I just
splitted
>> it. The Front end is still secured, but that back end
is
>> not. If someone were to go to the the backend folder on
>> the network, they could delete data. How do I secure
the
>> backend with the same Secured.mdw that is used on the
>> front end?
>>
>
>
>.
>

You're welcome!

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)


"Steve" <(E-Mail Removed)> wrote in message
news:2f7b01c49fe5$ca9ed2f0$(E-Mail Removed)...
> Excellent. Thanks.
> >-----Original Message-----
> >Hi, Steve.
> >
> >> I have an Access 2000 db that is secured. I just
> splitted
> >> it. The Front end is still secured, but that back end
> is
> >> not.
> >
> >That's the problem with using the Database Splitter
> Wizard. It completely
> >ignores security.
> >
> >To split it properly, one needs to make an extra copy of
> the unsplit
> >database and store that copy where the back end should
> be. Then, one should
> >delete all objects in this back end copy, except the
> tables and
> >relationships. Next, in the original database, the front
> end, the tables
> >should be deleted and new links created to the tables in
> the back end.
> >
> >HTH.
> >
> >Gunny
> >
> >See http://www.QBuilt.com for all your database needs.
> >See http://www.Access.QBuilt.com for Microsoft Access
> tips.
> >
> >(Please remove ZERO_SPAM from my reply E-mail address, so
> that a message
> >will be forwarded to me.)
> >
> >
> >"Steve" <(E-Mail Removed)> wrote in
> message
> >news:260d01c49f48$3a468ba0$(E-Mail Removed)...
> >> I have an Access 2000 db that is secured. I just
> splitted
> >> it. The Front end is still secured, but that back end
> is
> >> not. If someone were to go to the the backend folder on
> >> the network, they could delete data. How do I secure
> the
> >> backend with the same Secured.mdw that is used on the
> >> front end?
> >>
> >
> >
> >.
> >