Re: XP SP2 problem
- From: "Jure" <kupus2_at_hi_tocka_htnet_tocka_hr@xxxxxxxxxxxx>
- Date: Fri, 2 Jun 2006 18:36:40 +0200
"David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns97D5AA71C8DD2f99a49ed1d0c49c5bbb2@xxxxxxxxxxxx
"Jure" <kupus2_at_hi_tocka_htnet_tocka_hr@xxxxxxxxxxxx> wrote in
news:e5n30v$ski$1@xxxxxxxxxxxxxx:
Rows addes on XP SP2 machine wont replicate to other databases,
they have nulls in s_Generation column.
Is there a cure for this?
Newly added rows should be generation 0.
Are you saying that when you manually add a record to a table in
datasheet view, the s_Generation column remains Null?
Sounds like a major corruption of some sort.
I solved the problem. I use ADO and server side cursor to write changes in
database and during this process I initialize s_Generation column to null
because this is a generic procedure that copies values from my data storage
to recordset. On windows other than XP SP2 it works just fine but on XP SP2
null value is actually written in database. I can only say to good people in
Microsoft: don't fix it if it's not broken :))))
.
- Follow-Ups:
- Re: XP SP2 problem
- From: David W. Fenton
- Re: XP SP2 problem
- References:
- XP SP2 problem
- From: Jure
- Re: XP SP2 problem
- From: David W. Fenton
- XP SP2 problem
- Prev by Date: Re: Synchronization History AWOL
- Next by Date: Re: XP SP2 problem
- Previous by thread: Re: XP SP2 problem
- Next by thread: Re: XP SP2 problem
- Index(es):
Relevant Pages
|