Security on FE and BE

  • Thread starter Thread starter Steph
  • Start date Start date
S

Steph

I secured the FE of my database. That all went fine.
However, I would like to secure the BE as well, using the
same information so that when there is an attempt to log
on to the FE of the database by users, there aren't two
passwords or any locking out of the database going on.
Any hints as to how I can accomplish this?

Thanks!
 
Hi Steph,

Here's a thought that should help:

- Create your WorkGroup File *.MDW
- Join to the above WorkGroup File
- Create your BackEnd database
- Secure the objects as needed
- Create your FrontEnd database
- Secure the objects as needed

When user is joined the above *.MDW and opens your FrontEnd database that
is linked to the BackEnd database they are not prompted 2x (only the one
time).

Here's the type of shortcut they would have to launch your application:

"<full path to msaccess.exe>" "<full path to FE>" /wrkgrp "<full path to
above *.MDW file>"

I hope this helps! If you have additional questions on this topic, please
respond back to this posting.


Regards,

Eric Butts
Microsoft Access Support
(e-mail address removed)
"Microsoft Security Announcement: Have you installed the patch for
Microsoft Security Bulletin MS03-026? If not Microsoft strongly advises
you to review the information at the following link regarding Microsoft
Security Bulletin MS03-026
<http://www.microsoft.com/security/security_bulletins/ms03-026.asp> and/or
to visit Windows Update at <http://windowsupdate.microsoft.com/> to install
the patch. Running the SCAN program from the Windows Update site will help
to insure you are current with all security patches, not just MS03-026."

This posting is provided "AS IS" with no warranties, and confers no rights


--------------------
| Content-Class: urn:content-classes:message
| From: "Steph" <[email protected]>
| Sender: "Steph" <[email protected]>
| Subject: Security on FE and BE
| Date: Tue, 6 Apr 2004 15:23:39 -0700
| Lines: 8
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Thread-Index: AcQcJc/I5ZYURDF8QXe1JGLPLE6Btg==
| Newsgroups: microsoft.public.access.security
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.access.security:9747
| NNTP-Posting-Host: tk2msftngxa12.phx.gbl 10.40.1.164
| X-Tomcat-NG: microsoft.public.access.security
|
| I secured the FE of my database. That all went fine.
| However, I would like to secure the BE as well, using the
| same information so that when there is an attempt to log
| on to the FE of the database by users, there aren't two
| passwords or any locking out of the database going on.
| Any hints as to how I can accomplish this?
|
| Thanks!
|
 
Thanks for the quick response. The only thing is, I have
already split the database. So I was hoping I wouldn't
have to reimport everything. Should I just import the
tables (BE) to the already secured (FE) database and then
split it again?

Thanks!
 
Actually, ignore this message. I went ahead and
recreated the database and replaced the secured database
with one that was un-secured. So, I think I can pretty
easily follow your instructions now. I will just
recombine the database, secure it and then split it.
Thanks for the help!
 
Back
Top