Re: store secured.mdw data on sql?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: '69 Camaro (ForwardZERO_SPAM.To.69Camaro_at_Spameater.orgZERO_SPAM)
Date: 12/15/04 

Date: Wed, 15 Dec 2004 13:11:54 -0800

Hi.

> As to opening the database exclusively, who has
> control over how the fn.mdw file is opened?

When joining a workgroup, that Workgroup Information File will be opened in
shared mode so that up to 255 simultaneous users can be joined to the same
workgroup.

> We reference the security file
> name in the command line option that opens Access, and I assume that
Access
> itself determines the options under which it opens the fn.mdw at the time
of
> user login.

Correct.

> Although we have good backup plans, I'm concerned that we are going to
have
> to end up reloading the fn.mdw file periodically.

Workgroup Information (*.MDW) Files can become corrupted, but it is very,
very rare. Unless your workgroup adds or deletes users or groups often, or
changes passwords often, this file is fairly static. Restoring this file
from the backup taken the night before is sufficient for nearly all
organizations.

> It doesn't look good to the
> user community to see these errors and have to wait until we reload
something
> that should be stable.

Being proactive is a good thing. If the Access databases in your
organization are experiencing corruption on a regular basis, then you'll
need to investigate the cause. Access 2003 is probably the most stable
version yet, but database corruption still happens. Some of the most common
causes of database corruption are faulty network hardware, users turning off
the power to their PC's while Access still has the database open, and having
the Windows server OpLocks turned on.

HTH.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips.

(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)

"A. J." <AJ@discussions.microsoft.com> wrote in message
news:F7E6F601-FAE7-424B-9577-175C2F63B891@microsoft.com...
> We are using Access 2003. As to opening the database exclusively, who has
> control over how the fn.mdw file is opened? We reference the security file
> name in the command line option that opens Access, and I assume that
Access
> itself determines the options under which it opens the fn.mdw at the time
of
> user login.
>
> Although we have good backup plans, I'm concerned that we are going to
have
> to end up reloading the fn.mdw file periodically. It doesn't look good to
the
> user community to see these errors and have to wait until we reload
something
> that should be stable.
>
>
> "'69 Camaro" wrote:
>
> > Hi.
> >
> > > > > Can the secured.mdw file be split so that the data tables can be
> > stored on
> > > > SQL?
> >
> > No. Jet security wouldn't be very secure if one could easily delete the
> > tables in the *.MDW file and either replace them with tables of the same
> > name or link to tables in another database (with these tables containing
> > "known" data, of course).
> >
> > > The problem is that my secured.mdw got corrupted.
> >
> > You'll need to restore from backup or create a new secured.mdw file
using
> > the exact same identifier settings used to create the first one.
Hopefully,
> > you've recorded this information and saved it in a secure place if you
don't
> > have a backup.
> >
> > > It used to
> > > happen to our database back in the days before we put the data on SQL
and
> > > distributed the application to the user. Too many users in the
database at
> > > one time.
> >
> > "Too many users in the database at one time" does not cause database
> > corruption, unless the Access 97 (or earlier version) database was not
> > opened exclusively and design changes are being made and one or more
other
> > users opens the database. This situation is prevented in Access 2000
and
> > later versions. Otherwise, "Too many users in the database at one time"
may
> > cause annoying record locks and record update delays, but not database
> > corruption.
> >
> > HTH.
> >
> > Gunny
> >
> > See http://www.QBuilt.com for all your database needs.
> > See http://www.Access.QBuilt.com for Microsoft Access tips.
> >
> > (Please remove ZERO_SPAM from my reply E-mail address, so that a message
> > will be forwarded to me.)
> >
> >
> > "A. J." <AJ@discussions.microsoft.com> wrote in message
> > news:D546DCFB-9D3C-4501-8D39-355E04F05186@microsoft.com...
> > > Well, yes, I am. The problem is that my secured.mdw got corrupted. It
used
> > to
> > > happen to our database back in the days before we put the data on SQL
and
> > > distributed the application to the user. Too many users in the
database at
> > > one time. I'm idly wondering if we could do something like that with
the
> > > "secured.mdw" database.
> > >
> > > "Immanuel Sibero" wrote:
> > >
> > > > Hi A.J.
> > > >
> > > > Are you not using SQL security?
> > > >
> > > >
> > > > Immanuel Sibero
> > > >
> > > >
> > > >
> > > >
> > > > "A. J." <AJ@discussions.microsoft.com> wrote in message
> > > > news:CB4225A6-37A0-4A59-9BFD-1E3CC7A988DA@microsoft.com...
> > > > > Can the secured.mdw file be split so that the data tables can be
> > stored on
> > > > SQL?
> > > >
> > > >
> > > >
> >
> >
> >

Relevant Pages

  • Re: Repair corrupted forms
    ... Compact the database to get rid of this junk: ... Uncheck any references you do not need. ... Recovering from Corruption ... however having tried Access 2002 it opens ok. ...
    (microsoft.public.access.forms)
  • Re: Bypassing Login as Admin user
    ... her computer, but tries to open the database without even logging in, then ... (which can't happen because I have Admin set with no permissions). ... I checked her workgroup file, and she IS connected to the ... or incorrectly opens the database without the path and file name of ...
    (microsoft.public.access.security)
  • Re: 2002 database corrupt and unuseable after upgrading to Access 2003
    ... That will depend on the kind of corruption, but given that A2003 is barfing ... it sounds like you have a partially corrupted A2002 database. ... >>> opens the debugger to a module that isn't running at this point. ... >>> but then opening the VBA code produces the same sequence of errors. ...
    (microsoft.public.access.conversion)
  • Re: Setting up security level
    ... it will give you an option to 'join' a workgroup. ... but you would like to force your database to open with the ... computer and opens your database without signing on. ... There is a "Security FAQ" on the Microsoft website that talks about how to ...
    (microsoft.public.access.security)
  • Re: Bypassing Login as Admin user
    ... One more question:if the workgroup adminstrator is set for the correct file, ... >> attempting to bypass the login screen and go directly to the database as ... or incorrectly opens the database without the path and file name of ...
    (microsoft.public.access.security)