Re: Users locked out of secure DB

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Joan Wild (jwild_at_nospamtyenet.com)
Date: 02/26/04


Date: Thu, 26 Feb 2004 14:30:30 -0500

Hi Steve,

"Steve Kendrot" <anonymous@discussions.microsoft.com> wrote in message
news:2a2501c3fc91$e2f5c180$a101280a@phx.gbl...
> I just figured out why I couldn't copy and paste the FE
> throught the networks. Share permissions for the
> destination folders were set to read only

The destination folders? I assumed you were copying the frontend mdb to
each workstation; that's what you should do.

Split the database into frontend/backend. The backend (tables only) would
sit on your server. A copy of the frontend (linked to the backend) would be
put on each workstation.

Folder permissions must be set to full for the users. i.e. Both the folder
on the server where the backend is, and the folder on the workstation. The
users need to be able to create and delete the associated ldb files.

>
> I've been reading up on replication. Would you recommend
> going this route?

No. If all your users are on the same LAN, you don't need to use
replication.

> I think my plans are to have two
> databases. A stripped down version designed for users, and
> another designed for analysis of data. Is this a common
> practice?

If you split the database, you can create as many frontends linked to it as
you like.

>
> Also, what kind of systems do database managers use to
> keep track of queries etc... I find the DB gets confusing
> once I start building queries on queries. Many of my
> reports are built on tiered queries. I've often thought it
> would be convenient if access allowed subfolders in the
> database window to organize groups of related queries.

I haven't used the feature, but in Access 2002 (can't remember if 2000 has
this), you can create Groups in the database window; and then right-click an
object 'Add to Group'. Also you don't have to use saved queries as record
sources for forms/reports. You can use SQL statements - that might cut down
on the number of queries. As for keeping track, you can use Total Access
Analyzer from www.fmsinc.com to document *everything*. It's quite
extensive.

> Is
> there any way of generating a list of queries involved
> with creation of a specific report? I often create queries
> which I don't wind up using and if I'm not carefull about
> deleting them right away, I often forget if they are a
> vital component of some report.

TAA would help with this as well. A cheap, but time-consuming method is to
rename a suspect query to zname. Test your reports and see if you get any
errors.

>
> I'm a wildlife biologist with no computer background and
> stumble my way through this database development. It sure
> is nice to have a resource like this forum to turn to.
> Without folks like yourself who are so generous with their
> time and knowledge, I (and many others from the looks of
> it) would really be lost.

I used to be a forester and I stumbled in Access at first, too. I learned a
lot from newsgroups, so I'm here to give back a little (and I like helping
people).

Good luck!

-- 
Joan Wild
Microsoft Access MVP


Relevant Pages

  • Re: running report cause fatal error- on Win98, not XP
    ... It is actually not that difficult to crash JET with complex queries, ... another query. ... only the more complex reports cause the crash- the others do ... Then compact the database: ...
    (microsoft.public.access.reports)
  • Re: Any tips on working with a database that you did not create?
    ... am new to Access and taking over an entire database. ... In fact it had been thrown together using wizards ... Look through the queries and spot whether any of them are anything other ... Look at the reports. ...
    (microsoft.public.access.gettingstarted)
  • Re: Any tips on working with a database that you did not create?
    ... am new to Access and taking over an entire database. ... In fact it had been thrown together using wizards ... Look through the queries and spot whether any of them are anything other ... Look at the reports. ...
    (microsoft.public.access.gettingstarted)
  • Re: Any tips on working with a database that you did not create?
    ... I was given what looked like a "nearly finished" database which apparently represented a great deal of work. ... In fact it had been thrown together using wizards based on a wholly wrong table structure. ... Check to see if the database has "linked tables" - a common way of building a database is to put the tables in one file and all the queries, forms and reports in another, and link the two. ...
    (microsoft.public.access.gettingstarted)
  • Re: Designing a new DB
    ... Stay with one table and use queries and/or reports to group your data by ... ACC2002: Database Normalization Basics ... Database Normalization Tips by Luke Chung ... > There will be simple calculations in certain fields in both the> monthly and annual reports. ...
    (microsoft.public.access.gettingstarted)