write conflict from upsized .adp

[will eichert]

I'm getting the dreaded "Write Conflict" message. I just recently
upsized this from an .mdb to an .adp client/server db, and this msg
now appears. I can update a record once, but then if I update it again
(both times through a subform), I get the write conflict.

The subform's data is a view based on 2 tables. I set the uniquetable
property to the appropriate table. After upsizing, there's a timestamp
field in this table. When I look at it in datasheet view, all data in
the timestamp column is blank. Should values show up here? I used osql
to update every record in the field, still no timestamp data is
visible. I'm not sure the problem has anything to do with timestamps,
just grasping.

Any ideas out there?

Thanks,

Will Eichert
direct email = wfeichert[at]ucdavis.edu (replace [at] with @)

 

[Sylvain Lafontaine]

The possible causes for a "Write Conflict" under ADP are so numerous that I
won't take time trying to enumerate them here. You should read past
messages for this newsgroup and make a research on Google instead.

For the timestamp, you can try to remove it. (Don't forget to make a refresh
of your queries). Sometimes, this will resolve a Write Conflict and
sometimes, it will not. Many other things, like Nullable Bit fields and
some decimal fields, are also very problematic.

With ADP, you must make a lot of guess and try. Taking a look at the
queries sent by Access to the SQL-Server can also help in determining the
cause of a write conflict.

S. L.

 

[Steve Jorgensen]

I'm getting the dreaded "Write Conflict" message. I just recently
upsized this from an .mdb to an .adp client/server db, and this msg
now appears. I can update a record once, but then if I update it again
(both times through a subform), I get the write conflict.

The subform's data is a view based on 2 tables. I set the uniquetable
property to the appropriate table. After upsizing, there's a timestamp
field in this table. When I look at it in datasheet view, all data in
the timestamp column is blank. Should values show up here? I used osql
to update every record in the field, still no timestamp data is
visible. I'm not sure the problem has anything to do with timestamps,
just grasping.

Any ideas out there?

Thanks,

Will Eichert
direct email = wfeichert[at]ucdavis.edu (replace [at] with @)

I don't know if this is relate to your problem, but there is a bug with ADPs
and TIMESTAMP fields. I'd try removing the TIMESTAMP first, and see if that
helps. You'll eventually want to remove the TIMESTAMP anyway for your ADP app
to work properly.

 

[Hans Merkl]

I'm getting the dreaded "Write Conflict" message. I just recently
upsized this from an .mdb to an .adp client/server db, and this msg
now appears. I can update a record once, but then if I update it again
(both times through a subform), I get the write conflict.

The subform's data is a view based on 2 tables. I set the uniquetable
property to the appropriate table. After upsizing, there's a timestamp
field in this table. When I look at it in datasheet view, all data in
the timestamp column is blank. Should values show up here? I used osql
to update every record in the field, still no timestamp data is
visible. I'm not sure the problem has anything to do with timestamps,
just grasping.

Any ideas out there?

Thanks,

Will Eichert
direct email = wfeichert[at]ucdavis.edu (replace [at] with @)

I don't know if this is relate to your problem, but there is a bug with ADPs
and TIMESTAMP fields. I'd try removing the TIMESTAMP first, and see if that
helps. You'll eventually want to remove the TIMESTAMP anyway for your ADP app
to work properly.

Funny.For including a timestamp has solved a similar problem.

 

[will eichert]

Thanks to all that replied. I tried a few things, such as removing all
default values, removing the JOIN from the view (basing it on a single
table), and finally, removing the timestamp field from the table the
view is based on.

Removing the timestamp field did the trick. Does anyone know any more
about this? I thought SQL tables were supposed to have timestamps to
avoid write conflict errors?

Also, forgive my ignorance, but should I or should I not be able to
see timestamp data when in table datasheet view? In my tables, all of
the timestamp columns appear to be empty. Do they need to be
initialized somehow?

Anyway, thanks to Steve for the tip on removing the timestamp, I doubt
I would have thought of that.

Will

I'm getting the dreaded "Write Conflict" message. I just recently
upsized this from an .mdb to an .adp client/server db, and this msg
now appears. I can update a record once, but then if I update it again
(both times through a subform), I get the write conflict.

The subform's data is a view based on 2 tables. I set the uniquetable
property to the appropriate table. After upsizing, there's a timestamp
field in this table. When I look at it in datasheet view, all data in
the timestamp column is blank. Should values show up here? I used osql
to update every record in the field, still no timestamp data is
visible. I'm not sure the problem has anything to do with timestamps,
just grasping.

Any ideas out there?

Thanks,

Will Eichert
direct email = wfeichert[at]ucdavis.edu (replace [at] with @)

I don't know if this is relate to your problem, but there is a bug with ADPs
and TIMESTAMP fields. I'd try removing the TIMESTAMP first, and see if that
helps. You'll eventually want to remove the TIMESTAMP anyway for your ADP app
to work properly.