> Hello,

> We are experiencing problems with SQL Server access via an Access database
> using linked tables.

> Before the query 'why?' -- we are endeavouring to utilise a common code
base
> on an existing fat client product to get a first SQL version out the door,
> the system will be rewritten multi-tier soon.

> Anyway, the problems we are experiencing are related to yet another
> application architecture feature, bound controls. With IDENTITY fields and
> bound controls it is impossible not to use the dbSeeChanges option. Now,
the
> error message we get when we update a single data field when there is only
> one user connected to the database is 'The Microsoft Jet database engine
> stopped the processing because you and another user are attempting to
change
> the same data at the same time' and the system will not move to another
> record. I've looked on MSDN and this claims that this is related to the
> locking mechanism employed, but changes to locking are not having any
> impact.

> Is this a bug with the bound controls? Is it because we are going via an
> access database? We are pulling our hair out! Anyone have any thoughts
> please?

> Thanks

> Robert

> Hello,

> We are experiencing problems with SQL Server access via an Access database
> using linked tables.

> Before the query 'why?' -- we are endeavouring to utilise a common code
base
> on an existing fat client product to get a first SQL version out the door,
> the system will be rewritten multi-tier soon.

> Anyway, the problems we are experiencing are related to yet another
> application architecture feature, bound controls. With IDENTITY fields and
> bound controls it is impossible not to use the dbSeeChanges option. Now,
the
> error message we get when we update a single data field when there is only
> one user connected to the database is 'The Microsoft Jet database engine
> stopped the processing because you and another user are attempting to
change
> the same data at the same time' and the system will not move to another
> record. I've looked on MSDN and this claims that this is related to the
> locking mechanism employed, but changes to locking are not having any
> impact.

> Is this a bug with the bound controls? Is it because we are going via an
> access database? We are pulling our hair out! Anyone have any thoughts
> please?

> Thanks

> Robert

> You may have a corrupted Access database instead.  The error message you
get
> is the most common one reported with corrupted databases (see TechNet
> article Q182867).  You may have to create a new database and import what
you
> can.  This has happened to me several times and each time I lost one memo
> field but was able to recover everything else.  The access repair option
> hasn't helped me (also didn't report any error), nor has jetcomp (but
worth
> a try).  Corruption seems to happen with large Access databases from time
to
> time.

> > Hello,

> > We are experiencing problems with SQL Server access via an Access
database
> > using linked tables.

> > Before the query 'why?' -- we are endeavouring to utilise a common code
> base
> > on an existing fat client product to get a first SQL version out the
door,
> > the system will be rewritten multi-tier soon.

> > Anyway, the problems we are experiencing are related to yet another
> > application architecture feature, bound controls. With IDENTITY fields
and
> > bound controls it is impossible not to use the dbSeeChanges option. Now,
> the
> > error message we get when we update a single data field when there is
only
> > one user connected to the database is 'The Microsoft Jet database engine
> > stopped the processing because you and another user are attempting to
> change
> > the same data at the same time' and the system will not move to another
> > record. I've looked on MSDN and this claims that this is related to the
> > locking mechanism employed, but changes to locking are not having any
> > impact.

> > Is this a bug with the bound controls? Is it because we are going via an
> > access database? We are pulling our hair out! Anyone have any thoughts
> > please?

> > Thanks

> > Robert

> Add a SQL Server Timestamp datatype field to the table and try again.

> If it exists, Jet will use it to see if another user has modified the
record
> since it was cached. If the value is the same Jet will lock the record and
> then process the update.

> If there isn't a Timestamp field in the table then Jet will try to compare
> the value of EVERY field in the record to a cached value and with certain
> datatypes the comparison is inexact, thus causing the error you describe.
> --
> HTH
> Joe
> Check out Dev Ashish's web site for answers to common questions
> http://www.mvps.org/access/

> > Hello,

> > We are experiencing problems with SQL Server access via an Access
database
> > using linked tables.

> > Before the query 'why?' -- we are endeavouring to utilise a common code
> base
> > on an existing fat client product to get a first SQL version out the
door,
> > the system will be rewritten multi-tier soon.

> > Anyway, the problems we are experiencing are related to yet another
> > application architecture feature, bound controls. With IDENTITY fields
and
> > bound controls it is impossible not to use the dbSeeChanges option. Now,
> the
> > error message we get when we update a single data field when there is
only
> > one user connected to the database is 'The Microsoft Jet database engine
> > stopped the processing because you and another user are attempting to
> change
> > the same data at the same time' and the system will not move to another
> > record. I've looked on MSDN and this claims that this is related to the
> > locking mechanism employed, but changes to locking are not having any
> > impact.

> > Is this a bug with the bound controls? Is it because we are going via an
> > access database? We are pulling our hair out! Anyone have any thoughts
> > please?

> > Thanks

> > Robert