Re: Individual vs.whole dB locks on forms/reports during modificat

New groupies...that's rich.

Suggestion: Fix access so that users can once again modify forms while
others are logged in.
Answer: MS deliberately put this in Access 2000 because of the multitude of
problems with earlier versions that allowed people to edit database objects
like forms and reports while other users are in the database. It was a
major cause of database corruption.

Suggestion: Fix acesss so that users can once again modify reports while
others are logged in.
Answer: ditto above. Although you don't want to use Front-Ends, this is the
best practice. You don't get users walking all over each other's design
changes. Way back when Access allowed it, this was a constant headache for
the database developer.

Suggestion: Fix access so that a user is not allowed to put the whole
database in a locked state while others are logged in.
Answer: Not sure what you mean here. If you're talking about database
objects (forms, reports, etc.), then it's the same answer as above. If you
are talking about one user opening the database and then it's Read-Only by
everyone else, this is a Network Rights issue. If you're talking about
record-locking, you have to have something like this in any multi-user
database product.

Suggestion: Employ per form and per report level locks exactly like the
table locks so that other users can still access data even though someone is
creating a report or form for their own use
Answered above. You're repeating yourself.

Frankly, you're deliberately using the product incorrectly then complaining
about it. You don't use a wrench to pound nails and then wonder why it
doesn't work very well, do you?

--
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L



"mikebris@bmcd" <mikebrisbmcd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:FF842926-6836-44D3-87CC-FF7D42D11957@xxxxxxxxxxxxxxxx
> I didn't think new groupies would be reading this....
>
> But to answer your question, NO, there is no question, but there are
> implicit sugestions which is what the site is trying to collect..hence the
> big buttons where you can either agree or disagree to vote for a
> ...suggestion.
>
> So to spell them out for those who prefer not to analzye what they read,
my
> suggestions are:
>
> Fix access so that users can once again modify forms while others are
logged
> in.
> Fix acesss so that users can once again modify reports while others are
> logged in.
> Fix access so that a user is not allowed to put the whole database in a
> locked state while others are logged in.
> Employ per form and per report level locks exactly like the table locks so
> that other users can sill acess data even though someone is creating a
report
> or form for their own use.
>
> "Roger Carlson" wrote:
>
> > Is there a question here or do you just want to rant?
> >
> > --
> > --Roger Carlson
> > Access Database Samples: www.rogersaccesslibrary.com
> > Want answers to your Access questions in your Email?
> > Free subscription:
> > http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L
> >
> > "mikebris@bmcd" <mikebrisbmcd@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
> > news:EE3B455B-A271-482C-A467-EE8AC76A107B@xxxxxxxxxxxxxxxx
> > > MS underestimates how much on-the-fly use there is out here of access
DBs.
> > > In my engineering co we have teams of 5-10 users modifying data
directly
> > in
> > > the .mdb files all the time. Linked front ends are just too slow and
time
> > is
> > > money in all businesses. And no, we don't restrict users to forms
> > although
> > > we do use forms and reports to meet a particular need and those needs
> > change
> > > on an hourly basis.
> > >
> > > Locks should be smart enough to determine that if noone is using a
> > paticular
> > > form or report, modification is ok. How about a lock on the form, not
on
> > the
> > > whole database! Same as it is with tables, right?
> > >
> > > Here's another data integrity SNAFU, say a user opens a form for
modify
> > and
> > > they are notified that they cannot save changes because they do not
have
> > > exclusive access, and they select to go ahead and edit the
> > form....everyone
> > > is still locked out, until that user closes the form view and they
will
> > never
> > > be able to save their changes until everyone is logged out. A access
> > > stalemate!
> > >
> > > MS data integrity means 'prevent everyone from doing anything', or at
> > least
> > > make it hard enough that they lose the urge to try.
> > >
> > >
> > >
> > > ----------------
> > > This post is a suggestion for Microsoft, and Microsoft responds to the
> > > suggestions with the most votes. To vote for this suggestion, click
the "I
> > > Agree" button in the message pane. If you do not see the button,
follow
> > this
> > > link to open the suggestion in the Microsoft Web-based Newsreader and
then
> > > click "I Agree" in the message pane.
> > >
> > >
> >
http://www.microsoft.com/office/community/en-us/default.mspx?mid=ee3b455b-a271-482c-a467-ee8ac76a107b&dg=microsoft.public.access.forms
> >
> >
> >


.