store secured.mdw data on sql?

  • Thread starter Thread starter Guest
  • Start date Start date
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.
 
Hi.

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.
Click to expand...

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.
Click to expand...

"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.)
 
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.
 
Hi.
As to opening the database exclusively, who has
control over how the fn.mdw file is opened?
Click to expand...

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.
Click to expand...

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.
Click to expand...

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.)
 
I'm sorry if I haven't been clear, but the databases in our organization are
highly stable. It is the workgroup file which had the problem. I'm exploring
ways to make this last piece of the picture as stable as the other portions
which *are* under my control.
 
Hi, A. J.
It is the workgroup file which had the problem. I'm exploring
ways to make this last piece of the picture as stable as the other portions
which *are* under my control.
Click to expand...

Jet database files can become corrupted. The Workgroup Information File is
a Jet database file. It's very, very rare for the Workgroup Information
File to become corrupted because of the way it is used by Jet, but it
happened to yours.

One has control over which workgroup file to join and one has control -- to
a degree -- on the factors that cause database corruption. Remove the
factors that have a chance of corrupting the Workgroup Information File --
like 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 -- but keep a backup of this file just in case.

If you want to use Access, that's the only way to keep this part of the
picture highly stable for years to come.

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. said:
Can the secured.mdw file be split so that the data tables can be stored on
Click to expand...
SQL?

No.

And ADP/ADE uses SQL security.

If you import the workgroup tables to another mdb, it's 'not a workgroup
file'

You may consider giving each user their own copy of the workgroup file.

(david)
 
Back
Top