> So you suggest doing it as a Front-End / Back-End setup?
Yes, this is considered a "best practice".
> What happens with the Workgroup Security file...does that
> get installed with the front-end portion of the database
> on the users desktops or is it installed with the back-end
> on the NT server?
Yes. The front-end and back-end files must be secured separately using the
same
secure workgroup. If you haven't already, you can obtain the Access Security
FAQ
at:
http://support.microsoft.com/default.aspx?kbid=207793
--
Cheryl Fischer, MVP Microsoft Access
Law/Sys Associates, Houston, TX
"Ron" <(E-Mail Removed)> wrote in message
news:18fee01c41bfc$9388c860$(E-Mail Removed)...
> Cheryl,
>
> I'm actually in the process of redoing this entire
> database (better table structure, less form clutter, etc.)
> So you suggest doing it as a Front-End / Back-End setup?
> What happens with the Workgroup Security file...does that
> get installed with the front-end portion of the database
> on the users desktops or is it installed with the back-end
> on the NT server?
>
> Ron
>
> >-----Original Message-----
> >Ron,
> >
> >One of the most common reasons for the problems you
> report is having
> >multiple users opening the same copy of a database.
> Your application
> >should be split into a Front-End and a Back-End.
> >
> >The Front-End contains all Queries, Forms, Reports,
> Macros, Modules and
> >local-use tables. The Front-End contains links to the
> tables in the
> >Back-End, which contains only Tables containing data
> which is to be shared.
> >Each Front-End is then distributed to and run from each
> user's hard drive.
> >
> >
> >
> >--
> >
> >Cheryl Fischer, MVP Microsoft Access
> >Law/Sys Associates, Houston, TX
> >
> >
> >"Ron" <(E-Mail Removed)> wrote in
> message
> >news:1939501c41bf0$09bda120$(E-Mail Removed)...
> >> I am having a problem with a Network hosted, password
> >> authenticating AccessXP database.
> >> There are approximately 20 or so people that open and
> >> close this database at various intervals throughout the
> >> day, maybe 5 of them keep it open on a continual basis.
> >>
> >> Of course there is a .MDW security workgroup file stored
> >> on the network drive with the .MDB file and various
> levels
> >> of user accounts setup via the Security Wizard.
> >>
> >> The problem I'm having is that the database becomes
> >> corrupted on daily basis (sometimes 2 - 3x a day)and I
> >> have to repair and compact it everytime. This has
> become
> >> quite a nuisance and I can't figure out why this is
> >> happening. It even got so corrupted the other day that
> I
> >> had to restore a copy from 2 days prior because I
> couldn't
> >> repair it anymore.
> >> Does anyone have an idea as to why this is happening so
> >> often, and if so is there something that can be done to
> >> rectify it so it doesn't happen anymore?
> >>
> >> Please Help!
> >>
> >> Thanks - Ron
> >
> >
> >.
> >
Similar Threads
