As you can see below, I have had problems with inquisitive souls looking
at data they shouldn't be. I though disabling the ability to create new
databases using my workgroup would stop this but it doesn't. All they have
to do now is create a new database using the default wrkgroup, close it and
then open it again whilst joined to my workgroup and they can import again.
Can someone please help me stop these people importing from the FE or BE?
Many thanks,
Mark
"MacDermott" <ma********@nospam.com> wrote in message
news:6D*****************@newsread3.news.atl.earthl ink.net...
Do you have a reference to DAO?
From a code window, click Tools - References.
In the box that comes up, check Microsoft DAO Library.
Be sure to exit by using the OK button.
HTH
"Mark" <ma*********@ntlworld.com> wrote in message
news:iz************@newsfe2-gui.ntli.net...Hi All,
After countless hours of searching, I think I have found a solution
to
my problem from the Microsoft site (
http://support.microsoft.com/?kbid=210329 ). What is suggested is that I
disable the ability to create a new database when using my workgroup. As
the"inquisitive" person needs to create the database from within my
workgroup
to have permission to import, this seems like the perfect solution.
However, my programming skills are still in their infant stages and
thefunction provided by Microsoft does not work!!!!! The code below throws
up
the following error message when I try to run it: Compile error:
User-defined type not defined.
Could anyone please help me rectify this problem??
Function Remove_DBCreate()
Dim d As DAO.Database, c As Container, SystemDB As String
SystemDB = "C:\Program Files\Microsoft Office\" & _
"Office\System.mdw" ' Use path for your system.
Set d = DBEngine(0).OpenDatabase(SystemDB)
Set c = d.Containers!Databases
c.UserName = "Users"
c.Permissions = c.Permissions And Not dbSecDBCreate
End Function
TIA,
Mark
"Mark" <ma*********@ntlworld.com> wrote in message
news:XC*************@newsfe3-win.ntli.net...> Hi All,
>
> Firstly, I am aware from reading previous posts that if someone is
> determined enough, they will crack an Access Application. However, this
> problem seems basic but I can't find a workaround.
>
> I have a frontend/backend database at work which contains some
> sensitive information. I have used Access security along with my own
> and
> have disabled the shift key at start-up. I thought this was quite
> secure
> but I have found that someone has hacked into it and given themselves
> administrator privileges within my own security. After a lot of
> investigation, I have found out that they have done this by creating a
> new database under my workgroup and then importing the tables from the
> frontend. They can then open up any table they please and have
> visibility of everything due to no form being set to start-up..
>
> I have changed the way my security works by splitting the user table
> down so that the permissions given to each user is split from their
> passwords which they can change and given them only read permissions.
>
> What I want to be able to do is stop people being able to import/link
> from either the FE or BE unless they are the administrator. I have
> spent
> hours looking through the help files but can't see any reference to
> this.
>
> I am using Access 2002 SP2 on a XP platform.
>
> TIA
>
>
