Re: Record Locking problem

From: Mark A. Sam (msam_at_Plan-It-Earth.Net)
Date: 02/19/05 

Date: Sat, 19 Feb 2005 12:49:53 -0500

I have optimistic locking.

I opened two sessions and discovered that the first session allows editing,
but when I open the second session to the same record, it doesn't even allow
me to enter data as if the textboxes were locked. The same is true if I
open the table in the second copy, that I can't edit any fields.

I may just have to set the form to No Locks.

"JP" <jnospamperelst@optnospamonline.net> wrote in message
news:uKXkMYeFFHA.2296@TK2MSFTNGP15.phx.gbl...
> Ummm, what kind of locking do you have specified in the form itself. I
was
> assuming that you're using optimistic locking, but I shouldn't assume.
>
>
> "Mark A. Sam" <msam@Plan-It-Earth.Net> wrote in message
> news:ODK6a1UFFHA.1264@TK2MSFTNGP12.phx.gbl...
> > JP,
> >
> > It is a newword drive and not read only. We are able to enter data fine
> > unless the record is locked.
> >
> > Mark
> >
> > "JP" <jnospamperelst@optnospamonline.net> wrote in message
> > news:%23JAdHUUFFHA.1924@TK2MSFTNGP14.phx.gbl...
> > > Check and make sure that the mdb containing the data is not on a
> read-only
> > > drive, has not been defined as read-only, and that your users have
> update
> > > access on this particular drive. Is it a network drive?
> > >
> > >
> > > "Mark A. Sam" <msam@Plan-It-Earth.Net> wrote in message
> > > news:OdqmzJUFFHA.464@TK2MSFTNGP15.phx.gbl...
> > > > Hello JP,
> > > >
> > > > I debuged this and it is definately not not allowing the updating of
> > bound
> > > > text fields. If two people are on a record, nothing can be entered
> into
> > > any
> > > > of the fields. This is something I have never encountered, becuase
> even
> > > if
> > > > a record is locked, it should allow changes. This app has been
> > > operational
> > > > for 5 years. This is something new. In fact I am encountering
problems
> > of
> > > > different sorts from different apps at different locations. I think
> > maybe
> > > > Access 2K is self destructing ;)
> > > >
> > > > God Bless,
> > > >
> > > > Mark
> > > >
> > > >
> > > >
> > > >
> > > > "JP" <jnospamperelst@optnospamonline.net> wrote in message
> > > > news:eQsgyFUFFHA.3376@TK2MSFTNGP12.phx.gbl...
> > > > > The "you cannot assign a value to this object" is not usually a
> > message
> > > > that
> > > > > results from record locking issues.
> > > > >
> > > > > The most common cause of that message is when you are trying to
put
> > data
> > > > > into a field whose control source is defined as a calculation. In
> > that
> > > > > case, the field can't accept data that is type into the field or
any
> > vba
> > > > > assignment statements in events, etc.
> > > > >
> > > > > Does this problem happen when you only have one user?
> > > > >
> > > > >
> > > > > "Mark A. Sam" <msam@Plan-It-Earth.Net> wrote in message
> > > > > news:uYFt0HTFFHA.3032@TK2MSFTNGP12.phx.gbl...
> > > > > > I have an app running in Access 2K. When clicking a certain
> button,
> > > > some
> > > > > of
> > > > > > the textboxes on the form are updated. This particular app is
not
> > > > > allowing
> > > > > > and updated when multiple users are on the same record.
> > > > > >
> > > > > > The error is 2448: You cannot assign a value to this object.
> > > > > >
> > > > > > I dont't recall ever having this type of problem. Any ideas why
> > this
> > > > may
> > > > > be
> > > > > > occruring and how to fix it? Thanks and God Bless.
> > > > > >
> > > > > > Mark A. Sam
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>