Re: XP SP2 problem

"Jure" <kupus2_at_hi_tocka_htnet_tocka_hr@xxxxxxxxxxxx> wrote in
news:e5ppb0$66$1@xxxxxxxxxxxxxx:

"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
data*** 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 :))))

I didn't know you could edit data in the s_Generation field. It's a
Jet replication field, and I thought was completely unavailable for
any manipulation at all.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
.

Loading