MDE

[Connie]

I have a database that is an mde. I can can open it but
not any of the objects inside. A message appears when I
try to open for eg: a form and tells me I don't have
permission. No user id and password opion appears when
opening the db, and I am not allowed to make changes to
the security. Any suggestions on how to change the
permissions?

 

[Roxie Aho]

-----Original Message-----
I have a database that is an mde. I can can open it but
not any of the objects inside. A message appears when I
try to open for eg: a form and tells me I don't have
permission. No user id and password opion appears when
opening the db, and I am not allowed to make changes to
the security. Any suggestions on how to change the
permissions?
.

A developer creates an Access database, which is a MDB
file. When the application is ready to be distributed to
the users, the developer splits it into a backend that
contains only tables and a front end that contains
queries, forms, reports and the Visual Basic for
Applications code behind them. The developer converts the
front end (after making a copy) to a MDE file and
distributes that so users cannot change the design of
forms etc but are able to manipulate data.

If you are trying to open a form to change its design, you
can't do that.

If you are trying to open a form to view or modify data,
then it looks like you don't have permission for the back
end.

Ask your administrator or the person who developed/gave
you the MDE for permissions.

Roxie Aho
roxiea at usinternet.com

 

[Guest]

-----Original Message-----

A developer creates an Access database, which is a MDB
file. When the application is ready to be distributed to
the users, the developer splits it into a backend that
contains only tables and a front end that contains
queries, forms, reports and the Visual Basic for
Applications code behind them. The developer converts the
front end (after making a copy) to a MDE file and
distributes that so users cannot change the design of
forms etc but are able to manipulate data.

If you are trying to open a form to change its design, you
can't do that.

If you are trying to open a form to view or modify data,
then it looks like you don't have permission for the back
end.

Ask your administrator or the person who developed/gave
you the MDE for permissions.

Roxie Aho
roxiea at usinternet.com
.

Hi Roxie. Thanks for your reply. Unfortunately, the
individual who created the database has left the
organization's employ. The person who took over the
database attemped to convert the mde file, which was in
access 2.0, up to 2000. Now there is no accessing any
objects at all. No user id and p/w form opens. I would
be happy to just get the data out. New forms etc can be
created.

 

[Guest]

PS. the database is not split

A developer creates an Access database, which is a MDB
file. When the application is ready to be distributed to
the users, the developer splits it into a backend that
contains only tables and a front end that contains
queries, forms, reports and the Visual Basic for
Applications code behind them. The developer converts the
front end (after making a copy) to a MDE file and
distributes that so users cannot change the design of
forms etc but are able to manipulate data.

If you are trying to open a form to change its design, you
can't do that.

If you are trying to open a form to view or modify data,
then it looks like you don't have permission for the back
end.

Ask your administrator or the person who developed/gave
you the MDE for permissions.

Roxie Aho
roxiea at usinternet.com
.

 

[Douglas J. Steele]

Hi Roxie. Thanks for your reply. Unfortunately, the
individual who created the database has left the
organization's employ. The person who took over the
database attemped to convert the mde file, which was in
access 2.0, up to 2000. Now there is no accessing any
objects at all. No user id and p/w form opens. I would
be happy to just get the data out. New forms etc can be
created.

Something's not right here. MDE files weren't introduced until Access 97.

Getting the data out should be no problem. Create a new database, select
File | Get External Data | Import, then navigate to your database. You
should get the option to import any (or all) of the tables.

 

[Guest]

Something's not right here. MDE files weren't introduced until Access 97.

Getting the data out should be no problem. Create a new database, select
File | Get External Data | Import, then navigate to your database. You
should get the option to import any (or all) of the tables.

Thanks for your reply Doug. I do not know 2.0 at all, so
your input is gratefully received. I have already tried
to input the tables into a new database. I do not have
permission. What I'm thinking is that they are not
telling me everything. Someone has clearly tried their
hand at security and failed.

In such a case, do you know of any way to access the
data? I have a copy of the database that is not an mde
file and still the permissions are set and I can't open
move, change, import, export anything.

 

[Douglas J. Steele]

Thanks for your reply Doug. I do not know 2.0 at all, so
your input is gratefully received. I have already tried
to input the tables into a new database. I do not have
permission. What I'm thinking is that they are not
telling me everything. Someone has clearly tried their
hand at security and failed.

In such a case, do you know of any way to access the
data? I have a copy of the database that is not an mde
file and still the permissions are set and I can't open
move, change, import, export anything.

Access 2.0 security had a major hole in it that made it easy to get around.
Unfortunately, it's been so long since I worked with it that I can't
remember how to do it!

Hopefully someone else will chime in with the details. If you don't hear
from anyone in the next day or two, try reposting your question in the
microsoft.public.access.security group.

 

[connie]

Thank Doug. Nothing has worked, so I regretfully either
have to give it up, or find the original developer. I'd
love to know what that security hole is!!

Connie

Access 2.0 security had a major hole in it that made it
easy to get around.

 

[Douglas J. Steele]

Did you try posting to microsoft.public.access.security, as I suggested?