Split DB BE question

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Mary M - 25 Apr 2006 19:07 GMT

If you have a DB split using a FE and a BE can you put a password on the BE
db? Or will that cause the FE /BE not to work? Basically I don't want a user
to be able to open the BE db and see the tables, values ect. The FE is
already an mde application.

Thanks in advance.
.

Reply to this Message

Joan Wild - 25 Apr 2006 22:32 GMT

Yes you can. Once you've done that open the frontend, and delete the links.
Re-create them using File, Get External Data, Link and when you locate the
backend, it'll prompt you for the password (which will get stored with the
links).

However, you should know that the database password is easily cracked.

You could set an autoexec macro in the backend that pops up a message saying
"Access the data via the frontend", and follow that with the Quit Action.

You can then disable the shiftkey bypass on the backend.

Signature

Joan Wild
Microsoft Access MVP

> If you have a DB split using a FE and a BE can you put a password on
> the BE db? Or will that cause the FE /BE not to work? Basically I
[quoted text clipped - 3 lines]
> Thanks in advance.
> .

Reply to this Message

Mary M - 26 Apr 2006 13:51 GMT

> You could set an autoexec macro in the backend that pops up a message
> saying "Access the data via the frontend", and follow that with the Quit
> Action.
>
> You can then disable the shiftkey bypass on the backend.

Thanks, I thought of that but I couldn't figure out how to get into the
backend for modifications if the shift bypass was disabled. Any suggestions?
The FE already has the shift bypass disabled, so I keep a copy of the FE w/o
the bypass code so I can make edits.

Reply to this Message

Joan Wild - 26 Apr 2006 14:48 GMT

You can re-enable it from another mdb. Just change your code to refer to
the mdb with the shiftkey disabled, instead of CurrentDb(). Post the code
you're using if you don't understand what I mean.

You could also just use Albert Kallal's utility. It allows you to
disable/enable the shiftkey on any database. Look for By Pass Shift Key
Code on this page
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html

Signature

Joan Wild
Microsoft Access MVP

>> You could set an autoexec macro in the backend that pops up a message
>> saying "Access the data via the frontend", and follow that with the
[quoted text clipped - 6 lines]
> suggestions? The FE already has the shift bypass disabled, so I keep
> a copy of the FE w/o the bypass code so I can make edits.

Reply to this Message

Mary M - 26 Apr 2006 15:14 GMT

> You can re-enable it from another mdb. Just change your code to refer to
> the mdb with the shiftkey disabled, instead of CurrentDb(). Post the code
> you're using if you don't understand what I mean.

I don't know what you mean about using another mdb. Here is the code for the
FE

Private Sub Form_Open(Cancel As Integer)
DisableBypass
End Sub

Sub DisableBypass()

Dim prp As Property

On Error Resume Next
CurrentDb.Properties("AllowBypassKey") = False
If Err Then
Err.Clear
Set prp = CurrentDb.CreateProperty("AllowBypassKey", dbBoolean,
False)
CurrentDb.Properties.Append prp
Set prp = Nothing
End If
End Sub

Reply to this Message

Joan Wild - 26 Apr 2006 17:13 GMT

First you should realize that the code you have will only affect the mdb the
next time it is opened.

In a separate mdb, create a new module and put the following in it
Public Function setback()
Dim db As Database
Dim prop As Property, wrk As Workspace
Set wrk = DBEngine.Workspaces(0)
Set db = wrk.OpenDatabase("path to mdb that has shiftkey disabled")
On Error Resume Next
db.Properties.Delete "allowbypasskey"
Set prop = db.CreateProperty("allowbypasskey", dbBoolean, True)
db.Properties.Append prop
db.Properties("allowbypasskey") = True
Set prop = Nothing
Set db = Nothing
Set wrk = Nothing
End Function

Save the module with some name other than setback.

You can then just run the function from the immediate window.

Signature

Joan Wild
Microsoft Access MVP

>> You can re-enable it from another mdb. Just change your code to
>> refer to the mdb with the shiftkey disabled, instead of CurrentDb().
[quoted text clipped - 21 lines]
> End If
> End Sub

Reply to this Message

Mary M - 27 Apr 2006 13:55 GMT

> First you should realize that the code you have will only affect the mdb
> the next time it is opened.

Do you mean the code you supplied or the existing FE code?

Also, wouldn't any user be able to create an mdb, put the "re-enable" code
in a module, run it and gain access to the DB window or am I missing
something?

Thanks again.

Reply to this Message

Joan Wild - 27 Apr 2006 15:31 GMT

>> First you should realize that the code you have will only affect the
>> mdb the next time it is opened.
>
> Do you mean the code you supplied or the existing FE code?

I was referring to your existing code, but in fact it applies to both.

> Also, wouldn't any user be able to create an mdb, put the "re-enable"
> code in a module, run it and gain access to the DB window or am I
> missing something?

Of course. How likely do you think your users are to do this?

You could implement security, and then include the 4th argument in the
CreateProperty line, and set it to true. See
http://www.mvps.org/access/general/gen0040.htm

Then only a member of the Admins Group can set it back.

But then, Access security can be broken, and your users could reset it
anyway.

All you are/can really do is set up barriers. If you require absolute
security, then you shouldn't be using Jet as the backend data store. Use a
server-based system such as SQL Server.

Signature

Joan Wild
Microsoft Access MVP

Reply to this Message