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

Roger,

I gave him the answer to his locking problem. I don't know that he will
bother to try it. He is the kind of guy who will use a screwdriver as a
chisel and complain when it breaks.

"Roger Carlson" wrote:

> It's a very good thing that you're so good you don't need any help, because
> I fear with that attitude, you won't get any here.
>
> --
> --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:0E760B1F-DB40-4341-89BC-B1E529DAEC2A@xxxxxxxxxxxxxxxx
> > Quippy but useless, and how grandios does someone have to be to suppose
> they
> > know what someone else does or does not know or how they need to use a
> > database to perform their work. Do you work for Microsoft?
> >
> > Do I know VB - enough to get in trouble
> > Do I know VBA - enough to do what I need to.
> >
> > Do you have any idea of how I use Access, what kind of data I use it to
> > process, or how access speeds up my work? NO.
> >
> > Do you know how we use access to make 65000 wire terminations land in the
> > right spot at a power plant in Montana with use multiple tables and a
> couple
> > of queries and forms?
> >
> > Then shut up.
> >
> > Mike
> > Controls Engineer
> >
> >
> > "Klatuu" wrote:
> >
> > > Mike,
> > > You obviously don't know much about databases in general and Access in
> > > particular. If you did, you would be able to configure your database to
> > > overcome the issues you are complaining about.
> > >
> > > I suggest you do one of two things. Either find someone who is
> competent to
> > > structure your database so you can use it or "loose your urge to try"
> and use
> > > Excel instead.
> > >
> > >
> > >
> > > "mikebris@bmcd" wrote:
> > >
> > > > 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
>
>
>
.