Re: XP SP2 problem
- From: "Jure" <kupus2_at_hi_tocka_htnet_tocka_hr@xxxxxxxxxxxx>
- Date: Sat, 3 Jun 2006 09:42:35 +0200
"David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns97D6B4D773307f99a49ed1d0c49c5bbb2@xxxxxxxxxxxx
"Jure" <kupus2_at_hi_tocka_htnet_tocka_hr@xxxxxxxxxxxx> wrote in
news:e5qara$8u3$1@xxxxxxxxxxxxxx:
"David W. Fenton" <XXXusenet@xxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns97D68BB102B28f99a49ed1d0c49c5bbb2@xxxxxxxxxxxx
"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 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 :))))
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.
No, I didn't edit it, I created a new row, passed null through ADO
as initial value (before calling Update method) and database
accepted it instead of putting zero. I did the same for other
replication fields (s_GUID and others) but they are initialized
correctly.
Why in the world would you do that?
I would surmise that they are just like Autonumber fields, but if
you want the values in them to be correct, why would you pass a Null
as the value? The fields will initialize themselves correctly if you
don't pass any value to be appended into that field, so why would
you be mucking around with inserting values that are of no concern
to you?
We can argue what is wrong and what is right but I still think that
autonumber/system/read-only column shouldn't get confused when you try to
initialize it with some value. It should ignore it and preserve data
integriti. I keep my data in my own data structure and use server side
recordset for update. This way I have all then benefits as if I use client
side cursor and the update speed of server side cursors (update of client
side recordset is much slower) plus correct handling of transactions
(Rollback transaction won't work with client side recordsets, they won't
update correctly next time). So, when I add a new row I call ADO's method
AddNew and pass array with names of all the columns and array with all the
values. Second array has null value for s_Generation column and it is a
problen on XP SP2 machines.
.
- 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
- Re: XP SP2 problem
- From: Jure
- Re: XP SP2 problem
- From: David W. Fenton
- Re: XP SP2 problem
- From: Jure
- Re: XP SP2 problem
- From: David W. Fenton
- XP SP2 problem
- Prev by Date: Re: XP SP2 problem
- 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
|