security worry on workgroup file

[Paul T. Rong]

A card where I wrote my name and WID (work group ID) was stolen
(unfortunately together with other things), therotically the one who have my
name and WID can create the same mdw file which I use with my database.

Who can tell me can it have any influnce on the security of my database?

If nothing, I will just ignore it.

If yes, what can I do? Is it possible somewhere that I can change my WID of
the mdw file? Or should I export all tables, forms etc. to an empty mdb file
(using the access default system.mdw file), and to start to make a new work
group file?

I love access, but the security drives me nuts.

Thanks,

Paul from Bratislava, Slovakia

[Terry Kreft]

If they have the information to recreate the system mdb and th eUser
accounts especially the system admin accounts then yes they can get at your
data.

If you believe this to be the case then you should create a new system db
and export your db objects to a new db and resecure.

Have a look at
http://www.trigeminal.com/lang/1033/...p?ItemID=10#10

which may wel be of use to you.
--
Terry Kreft
MVP Microsoft Access
"Paul T. Rong" <et***@hotmail.com> wrote in message
news:Nt******************@news.chello.at...

A card where I wrote my name and WID (work group ID) was stolen
(unfortunately together with other things), therotically the one who have my name and WID can create the same mdw file which I use with my database.

Who can tell me can it have any influnce on the security of my database?

If nothing, I will just ignore it.

If yes, what can I do? Is it possible somewhere that I can change my WID of the mdw file? Or should I export all tables, forms etc. to an empty mdb file (using the access default system.mdw file), and to start to make a new work group file?

I love access, but the security drives me nuts.

Thanks,

Paul from Bratislava, Slovakia

[Paul RONG]

Thanks Terry for your precious advise.

The fact is they have only got my name and the WID (work group ID
number) of the mdw file,
They don't have any User accounts nor the admin accounts.
Beside, my db is a mde file.

So this is the case.

Do you think in this case do I still have to export my db objects to a
new db and resecure?

You are famous among the access fans, it is my honor to get mails from
you. Thanks again.

Paul T. RONG
Benediktiho 4
Bratislava
Slovakia

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Terry Kreft]

Compiling to MDE protects your code, workgroup security protects your data
(and your code).

If your data is important and you think that the data could be breached and
misused then I would have thought you would need to resecure.

Really thouh you are the only person who can answer whether you need to do
this.

With the WID and Admin name they're at the door all they need is the key
(your password) nad they're probably in.

--
Terry Kreft
MVP Microsoft Access
"Paul RONG" <et***@hotmail.com> wrote in message
news:40*********************@news.frii.net...

Thanks Terry for your precious advise.

The fact is they have only got my name and the WID (work group ID
number) of the mdw file,
They don't have any User accounts nor the admin accounts.
Beside, my db is a mde file.

So this is the case.

Do you think in this case do I still have to export my db objects to a
new db and resecure?

You are famous among the access fans, it is my honor to get mails from
you. Thanks again.

Paul T. RONG
Benediktiho 4
Bratislava
Slovakia

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Paul T. Rong]

Dear me, I am sweating when I read your mail. Never thought Access security
is so fragile. Thanks for advise. I think I am gonna export all objects to
an empty db to rescure.

I tried export, but everytime only one object was allowed, so it was very
slow, and it is said that the tables' relationship can not be exported. Do
you know any better way to do that?

Or is it possible for me to get rid of the mdw file which is bounded
together with the DB?

Paul T. RONG
Benediktiho 4
Bratislava
Slovakia


"Terry Kreft" <te*********@mps.co.uk> дÈëÏûÏ¢ÐÂÎÅ
:w4********************@karoo.co.uk...

Compiling to MDE protects your code, workgroup security protects your data
(and your code).

If your data is important and you think that the data could be breached and misused then I would have thought you would need to resecure.

Really thouh you are the only person who can answer whether you need to do
this.

With the WID and Admin name they're at the door all they need is the key
(your password) nad they're probably in.

--
Terry Kreft
MVP Microsoft Access
"Paul RONG" <et***@hotmail.com> wrote in message
news:40*********************@news.frii.net...

Thanks Terry for your precious advise.

The fact is they have only got my name and the WID (work group ID
number) of the mdw file,
They don't have any User accounts nor the admin accounts.
Beside, my db is a mde file.

So this is the case.

Do you think in this case do I still have to export my db objects to a
new db and resecure?

You are famous among the access fans, it is my honor to get mails from
you. Thanks again.

Paul T. RONG
Benediktiho 4
Bratislava
Slovakia

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Paul T. Rong]

Terry, By the way, you said, "Compiling to MDE protects your code, workgroup
security protects your data (AND YOUR CODE)", does it mean, that someone who
controled my workgroup security can read codes in a MDE file? I was
astonished....
"Paul T. Rong" <et***@hotmail.com> дÈëÏûÏ¢ÐÂÎÅ
:Iw******************@news.chello.at...

Dear me, I am sweating when I read your mail. Never thought Access security is so fragile. Thanks for advise. I think I am gonna export all objects to
an empty db to rescure.

I tried export, but everytime only one object was allowed, so it was very
slow, and it is said that the tables' relationship can not be exported. Do
you know any better way to do that?

Or is it possible for me to get rid of the mdw file which is bounded
together with the DB?

Paul T. RONG
Benediktiho 4
Bratislava
Slovakia


"Terry Kreft" <te*********@mps.co.uk> дÈëÏûÏ¢ÐÂÎÅ
:w4********************@karoo.co.uk...

Compiling to MDE protects your code, workgroup security protects your data (and your code).

If your data is important and you think that the data could be breached

and

misused then I would have thought you would need to resecure.

Really thouh you are the only person who can answer whether you need to do this.

With the WID and Admin name they're at the door all they need is the key
(your password) nad they're probably in.

--
Terry Kreft
MVP Microsoft Access
"Paul RONG" <et***@hotmail.com> wrote in message
news:40*********************@news.frii.net...

Thanks Terry for your precious advise.

The fact is they have only got my name and the WID (work group ID
number) of the mdw file,
They don't have any User accounts nor the admin accounts.
Beside, my db is a mde file.

So this is the case.

Do you think in this case do I still have to export my db objects to a
new db and resecure?

You are famous among the access fans, it is my honor to get mails from
you. Thanks again.

Paul T. RONG
Benediktiho 4
Bratislava
Slovakia

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Paul T. Rong]

Terry, excuse me, but I really didn't get you when you say "workgroup
security protects your data (AND YOUR CODE)", I think workgroup security
protects only the data in the case of MDE file, because according to the
Access Help file, no one (including the one who controled my workgroup
securtiy) can see codes inside a MDE file.

I really hate to export my DB objects to rescure, if I know theoretically my
codes are safe, then I will leave it what it is.

best regards,

Paul
"Paul T. Rong" <et***@hotmail.com> дÈëÏûÏ¢ÐÂÎÅ
:RD******************@news.chello.at...

Terry, By the way, you said, "Compiling to MDE protects your code, workgroup security protects your data (AND YOUR CODE)", does it mean, that someone who controled my workgroup security can read codes in a MDE file? I was
astonished....
"Paul T. Rong" <et***@hotmail.com> дÈëÏûÏ¢ÐÂÎÅ
:Iw******************@news.chello.at...

Dear me, I am sweating when I read your mail. Never thought Access security

is so fragile. Thanks for advise. I think I am gonna export all objects to

an empty db to rescure.

I tried export, but everytime only one object was allowed, so it was very slow, and it is said that the tables' relationship can not be exported. Do you know any better way to do that?

Or is it possible for me to get rid of the mdw file which is bounded
together with the DB?

Paul T. RONG
Benediktiho 4
Bratislava
Slovakia


"Terry Kreft" <te*********@mps.co.uk> дÈëÏûÏ¢ÐÂÎÅ
:w4********************@karoo.co.uk...

Compiling to MDE protects your code, workgroup security protects your data (and your code).

If your data is important and you think that the data could be breached and

misused then I would have thought you would need to resecure.

Really thouh you are the only person who can answer whether you need

to do this.

With the WID and Admin name they're at the door all they need is the

key (your password) nad they're probably in.

--
Terry Kreft
MVP Microsoft Access
"Paul RONG" <et***@hotmail.com> wrote in message
news:40*********************@news.frii.net...
> Thanks Terry for your precious advise.
>
> The fact is they have only got my name and the WID (work group ID
> number) of the mdw file,
> They don't have any User accounts nor the admin accounts.
> Beside, my db is a mde file.
>
> So this is the case.
>
> Do you think in this case do I still have to export my db objects to a > new db and resecure?
>
> You are famous among the access fans, it is my honor to get mails from > you. Thanks again.
>
> Paul T. RONG
> Benediktiho 4
> Bratislava
> Slovakia
>
>
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

[Terry Kreft]

Paul,
Maybe I was being to cryptic.

If you have an MDB file and you apply workgroup security properly then your
data and your code are protected, because you haev to have the righ
permissions in order to see the raw data and to open forms etc in design
view so you can get to the code.

If you compile an MDB to MDE then the source code is stripped and just the
compiled code is left so they cannot view the code as it is no longer there.
--
Terry Kreft
MVP Microsoft Access
"Paul T. Rong" <et***@hotmail.com> wrote in message
news:rT******************@news.chello.at...

Terry, excuse me, but I really didn't get you when you say "workgroup
security protects your data (AND YOUR CODE)", I think workgroup security
protects only the data in the case of MDE file, because according to the
Access Help file, no one (including the one who controled my workgroup
securtiy) can see codes inside a MDE file.

I really hate to export my DB objects to rescure, if I know theoretically my codes are safe, then I will leave it what it is.

best regards,

Paul
"Paul T. Rong" <et***@hotmail.com> дÈëÏûÏ¢ÐÂÎÅ
:RD******************@news.chello.at...

Terry, By the way, you said, "Compiling to MDE protects your code, workgroup

security protects your data (AND YOUR CODE)", does it mean, that someone

who

controled my workgroup security can read codes in a MDE file? I was
astonished....
"Paul T. Rong" <et***@hotmail.com> дÈëÏûÏ¢ÐÂÎÅ
:Iw******************@news.chello.at...

Dear me, I am sweating when I read your mail. Never thought Access

security

is so fragile. Thanks for advise. I think I am gonna export all

objects to an empty db to rescure.

I tried export, but everytime only one object was allowed, so it was very slow, and it is said that the tables' relationship can not be

exported.

Do you know any better way to do that?

Or is it possible for me to get rid of the mdw file which is bounded
together with the DB?

Paul T. RONG
Benediktiho 4
Bratislava
Slovakia


"Terry Kreft" <te*********@mps.co.uk> дÈëÏûÏ¢ÐÂÎÅ
:w4********************@karoo.co.uk...
> Compiling to MDE protects your code, workgroup security protects

your

data

> (and your code).
>
> If your data is important and you think that the data could be

breached and
> misused then I would have thought you would need to resecure.
>
> Really thouh you are the only person who can answer whether you need to

do

> this.
>
> With the WID and Admin name they're at the door all they need is the

key > (your password) nad they're probably in.
>
> --
> Terry Kreft
> MVP Microsoft Access
>
>
> "Paul RONG" <et***@hotmail.com> wrote in message
> news:40*********************@news.frii.net...
> > Thanks Terry for your precious advise.
> >
> > The fact is they have only got my name and the WID (work group ID
> > number) of the mdw file,
> > They don't have any User accounts nor the admin accounts.
> > Beside, my db is a mde file.
> >
> > So this is the case.
> >
> > Do you think in this case do I still have to export my db objects

to a > > new db and resecure?
> >
> > You are famous among the access fans, it is my honor to get mails from > > you. Thanks again.
> >
> > Paul T. RONG
> > Benediktiho 4
> > Bratislava
> > Slovakia
> >
> >
> >
> > *** Sent via Developersdex http://www.developersdex.com ***
> > Don't just participate in USENET...get rewarded for it!
>
>