We are currently migrating our app from SYbase to MS-SQL
Server 2008. We are using PB11.5 & connecting to MS-SQL
Server using the PB Native Driver (SQLNCLI10).

In one of the windows we are getting "Row changed between
Retrieve & Update". Can anybody give a clue why this might
be happening.

The window works perfectly in SybaseBUT is failing in
MS_SQL.I know the the general reason for getting this msg.
BUT what we are surprised is that this works great in Sybase
& for some reason fails in MS_SQL Server. I know for sure
that I am the only one accessing this data so there is no
reason for getting the "ROW CHANGED.." error. The DW has of
course 'key & updateable columns' & if we change to 'key
columns' this might work in MS-SQL.
BUT want to know what could be the cause for this to fail in
MS-SQL. Has anybody else experienced this when migrating
from Sybase to MS-SQL Server2008
Thnx
Anil

What's the datatype of the key column?   Timestamp columns operate 
differently in Sybase (which is a company, not a DBMS - we have 5 different 
DBMS products...) than in MS-SQL.

Paul Horan[Sybase]
http://paulhoran.ulitzer.com

<anil> wrote in message news:4cf86867.775f.1681692777@sybase.com...
> We are currently migrating our app from SYbase to MS-SQL
> Server 2008. We are using PB11.5 & connecting to MS-SQL
> Server using the PB Native Driver (SQLNCLI10).
>
> In one of the windows we are getting "Row changed between
> Retrieve & Update". Can anybody give a clue why this might
> be happening.
>
> The window works perfectly in SybaseBUT is failing in
> MS_SQL.I know the the general reason for getting this msg.
> BUT what we are surprised is that this works great in Sybase
> & for some reason fails in MS_SQL Server. I know for sure
> that I am the only one accessing this data so there is no
> reason for getting the "ROW CHANGED.." error. The DW has of
> course 'key & updateable columns' & if we change to 'key
> columns' this might work in MS-SQL.
> BUT want to know what could be the cause for this to fail in
> MS-SQL. Has anybody else experienced this when migrating
> from Sybase to MS-SQL Server2008
> Thnx
> Anil 

Hi Anil;

  Sorry to hear that you have had to downgrade your DBMS!  :-))))

I suspect that changing the DW update to Key only will be the ticket. I 
think the problem might be due to checking the updatable columns where maybe 
the DBA has added a trigger that is updating something, changed a data type 
thus the columns behaviour, etc.

HTH

Regards ... Chris
President: OSUG / STD Inc.
Blog: http://chrispollach.blogspot.com
PBDJ: http://chrispollach.sys-con.com
SourceForge: http://sourceforge.net/projects/stdfndclass

"anil" wrote in message news:4cf86867.775f.1681692777@sybase.com...

We are currently migrating our app from SYbase to MS-SQL
Server 2008. We are using PB11.5 & connecting to MS-SQL
Server using the PB Native Driver (SQLNCLI10).

In one of the windows we are getting "Row changed between
Retrieve & Update". Can anybody give a clue why this might
be happening.

The window works perfectly in SybaseBUT is failing in
MS_SQL.I know the the general reason for getting this msg.
BUT what we are surprised is that this works great in Sybase
& for some reason fails in MS_SQL Server. I know for sure
that I am the only one accessing this data so there is no
reason for getting the "ROW CHANGED.." error. The DW has of
course 'key & updateable columns' & if we change to 'key
columns' this might work in MS-SQL.
BUT want to know what could be the cause for this to fail in
MS-SQL. Has anybody else experienced this when migrating
from Sybase to MS-SQL Server2008
Thnx
Anil 

In addition to what Chris said you may want to look at the
RecheckRows dbparm.


> Hi Anil;
>
>   Sorry to hear that you have had to downgrade your DBMS!
> :-))))
>
> I suspect that changing the DW update to Key only will be
> the ticket. I  think the problem might be due to checking
> the updatable columns where maybe  the DBA has added a
> trigger that is updating something, changed a data type
> thus the columns behaviour, etc.
>
> HTH
>
> Regards ... Chris
> President: OSUG / STD Inc.
> Blog: http://chrispollach.blogspot.com
> PBDJ: http://chrispollach.sys-con.com
> SourceForge: http://sourceforge.net/projects/stdfndclass
>
> "anil" wrote in message
> news:4cf86867.775f.1681692777@sybase.com...
>
> We are currently migrating our app from SYbase to MS-SQL
> Server 2008. We are using PB11.5 & connecting to MS-SQL
> Server using the PB Native Driver (SQLNCLI10).
>
> In one of the windows we are getting "Row changed between
> Retrieve & Update". Can anybody give a clue why this might
> be happening.
>
> The window works perfectly in SybaseBUT is failing in
> MS_SQL.I know the the general reason for getting this msg.
> BUT what we are surprised is that this works great in
> Sybase & for some reason fails in MS_SQL Server. I know
> for sure that I am the only one accessing this data so
> there is no reason for getting the "ROW CHANGED.." error.
> The DW has of course 'key & updateable columns' & if we
> change to 'key columns' this might work in MS-SQL.
> BUT want to know what could be the cause for this to fail
> in MS-SQL. Has anybody else experienced this when
> migrating from Sybase to MS-SQL Server2008
> Thnx
> Anil
>

Hello Chris
Yes. Its unfortunate that we are forced to downgrade. Been
working in Sybase for the last 15 years. Blame it on Mgmt.
:(

I was researching on this issue &found a link where Bruce
Armstrong had suggested to put SET NOCOUNT ON in the
trigger. Adding this, my data is saving & I am not getting
any error. But I am not understanding how NOCOUNT ON can
resolve this problem. I am just worried if this is the
correct solution OR this is just masking the error.
How can SET NOCOUNT ON mask this error & is this the correct
solution?
Anil

> Hi Anil;
>
>   Sorry to hear that you have had to downgrade your DBMS!
> :-))))
>
> I suspect that changing the DW update to Key only will be
> the ticket. I  think the problem might be due to checking
> the updatable columns where maybe  the DBA has added a
> trigger that is updating something, changed a data type
> thus the columns behaviour, etc.
>
> HTH
>
> Regards ... Chris
> President: OSUG / STD Inc.
> Blog: http://chrispollach.blogspot.com
> PBDJ: http://chrispollach.sys-con.com
> SourceForge: http://sourceforge.net/projects/stdfndclass
>
> "anil" wrote in message
> news:4cf86867.775f.1681692777@sybase.com...
>
> We are currently migrating our app from SYbase to MS-SQL
> Server 2008. We are using PB11.5 & connecting to MS-SQL
> Server using the PB Native Driver (SQLNCLI10).
>
> In one of the windows we are getting "Row changed between
> Retrieve & Update". Can anybody give a clue why this might
> be happening.
>
> The window works perfectly in SybaseBUT is failing in
> MS_SQL.I know the the general reason for getting this msg.
> BUT what we are surprised is that this works great in
> Sybase & for some reason fails in MS_SQL Server. I know
> for sure that I am the only one accessing this data so
> there is no reason for getting the "ROW CHANGED.." error.
> The DW has of course 'key & updateable columns' & if we
> change to 'key columns' this might work in MS-SQL.
> BUT want to know what could be the cause for this to fail
> in MS-SQL. Has anybody else experienced this when
> migrating from Sybase to MS-SQL Server2008
> Thnx
> Anil
>

Hi Anil;

   Pretty much the same here in Canada's capital. Most ASE shops have now 
switched to SS due to management pressure.  :-(


Regards ... Chris
President: OSUG / STD Inc.
Blog: http://chrispollach.blogspot.com
PBDJ: http://chrispollach.sys-con.com
SourceForge: http://sourceforge.net/projects/stdfndclass

"Anil" wrote in message news:4cf9733b.2473.1681692777@sybase.com...

Hello Chris
Yes. Its unfortunate that we are forced to downgrade. Been
working in Sybase for the last 15 years. Blame it on Mgmt.
:(

I was researching on this issue &found a link where Bruce
Armstrong had suggested to put SET NOCOUNT ON in the
trigger. Adding this, my data is saving & I am not getting
any error. But I am not understanding how NOCOUNT ON can
resolve this problem. I am just worried if this is the
correct solution OR this is just masking the error.
How can SET NOCOUNT ON mask this error & is this the correct
solution?
Anil

> Hi Anil;
>
>   Sorry to hear that you have had to downgrade your DBMS!
> :-))))
>
> I suspect that changing the DW update to Key only will be
> the ticket. I  think the problem might be due to checking
> the updatable columns where maybe  the DBA has added a
> trigger that is updating something, changed a data type
> thus the columns behaviour, etc.
>
> HTH
>
> Regards ... Chris
> President: OSUG / STD Inc.
> Blog: http://chrispollach.blogspot.com
> PBDJ: http://chrispollach.sys-con.com
> SourceForge: http://sourceforge.net/projects/stdfndclass
>
> "anil" wrote in message
> news:4cf86867.775f.1681692777@sybase.com...
>
> We are currently migrating our app from SYbase to MS-SQL
> Server 2008. We are using PB11.5 & connecting to MS-SQL
> Server using the PB Native Driver (SQLNCLI10).
>
> In one of the windows we are getting "Row changed between
> Retrieve & Update". Can anybody give a clue why this might
> be happening.
>
> The window works perfectly in SybaseBUT is failing in
> MS_SQL.I know the the general reason for getting this msg.
> BUT what we are surprised is that this works great in
> Sybase & for some reason fails in MS_SQL Server. I know
> for sure that I am the only one accessing this data so
> there is no reason for getting the "ROW CHANGED.." error.
> The DW has of course 'key & updateable columns' & if we
> change to 'key columns' this might work in MS-SQL.
> BUT want to know what could be the cause for this to fail
> in MS-SQL. Has anybody else experienced this when
> migrating from Sybase to MS-SQL Server2008
> Thnx
> Anil
> 

Hi Chris,
I would partly blame this on Sybase too. We have been
migrating our app. for the last 2 months & with my 'limited'
experience of using ms-sql during this short period, I am
actually seeing some pretty strong reasons for taking a
stand on MS_SQL Server.

The sad thing is our mgmt were also seriously thinking of
replacing PB with C# BUT due to the huge size of our app.,
risk & the budget to convert to C#, we are now thinking of
having a mix of PB & C# wen we migrate to PB12.NET.
Eventually a day will come soon when our app. will be
replaced by C#. This will be the saddest day of my
professional life.

Anyway, Chris - Pl. advice as to how SET NOCOUNT ON  can fix
the issue.

Thnx
Anil
> Hi Anil;
>
>    Pretty much the same here in Canada's capital. Most ASE
> shops have now  switched to SS due to management pressure.
>  :-(
>
>
> Regards ... Chris
> President: OSUG / STD Inc.
> Blog: http://chrispollach.blogspot.com
> PBDJ: http://chrispollach.sys-con.com
> SourceForge: http://sourceforge.net/projects/stdfndclass
>
> "Anil" wrote in message
> news:4cf9733b.2473.1681692777@sybase.com...
>
> Hello Chris
> Yes. Its unfortunate that we are forced to downgrade. Been
> working in Sybase for the last 15 years. Blame it on Mgmt.
> :(
>
> I was researching on this issue &found a link where Bruce
> Armstrong had suggested to put SET NOCOUNT ON in the
> trigger. Adding this, my data is saving & I am not getting
> any error. But I am not understanding how NOCOUNT ON can
> resolve this problem. I am just worried if this is the
> correct solution OR this is just masking the error.
> How can SET NOCOUNT ON mask this error & is this the
> correct solution?
> Anil
>
> > Hi Anil;
> >
> >   Sorry to hear that you have had to downgrade your
> > DBMS! :-))))
> >
> > I suspect that changing the DW update to Key only will
> > be the ticket. I  think the problem might be due to
> > checking the updatable columns where maybe  the DBA has
> > added a trigger that is updating something, changed a
> > data type thus the columns behaviour, etc.
> >
> > HTH
> >
> > Regards ... Chris
> > President: OSUG / STD Inc.
> > Blog: http://chrispollach.blogspot.com
> > PBDJ: http://chrispollach.sys-con.com
> > SourceForge: http://sourceforge.net/projects/stdfndclass
> >
> > "anil" wrote in message
> > news:4cf86867.775f.1681692777@sybase.com...
> >
> > We are currently migrating our app from SYbase to MS-SQL
> > Server 2008. We are using PB11.5 & connecting to MS-SQL
> > Server using the PB Native Driver (SQLNCLI10).
> >
> > In one of the windows we are getting "Row changed
> > between Retrieve & Update". Can anybody give a clue why
> > this might be happening.
> >
> > The window works perfectly in SybaseBUT is failing in
> > MS_SQL.I know the the general reason for getting this
> > msg. BUT what we are surprised is that this works great
> > in Sybase & for some reason fails in MS_SQL Server. I
> > know for sure that I am the only one accessing this data
> > so there is no reason for getting the "ROW CHANGED.."
> > error. The DW has of course 'key & updateable columns' &
> > if we change to 'key columns' this might work in MS-SQL.
> > BUT want to know what could be the cause for this to
> > fail in MS-SQL. Has anybody else experienced this when
> > migrating from Sybase to MS-SQL Server2008
> > Thnx
> > Anil
> >
>

The datatype is tinyint.
The sybase product is the DBMS ASE 12.5.2
Anil

> What's the datatype of the key column?   Timestamp columns
> operate  differently in Sybase (which is a company, not a
> DBMS - we have 5 different  DBMS products...) than in
> MS-SQL.
>
> Paul Horan[Sybase]
> http://paulhoran.ulitzer.com
>
> <anil> wrote in message
> > news:4cf86867.775f.1681692777@sybase.com... We are
> > currently migrating our app from SYbase to MS-SQL Server
> > 2008. We are using PB11.5 & connecting to MS-SQL Server
> using the PB Native Driver (SQLNCLI10). >
> > In one of the windows we are getting "Row changed
> > between Retrieve & Update". Can anybody give a clue why
> > this might be happening.
> >
> > The window works perfectly in SybaseBUT is failing in
> > MS_SQL.I know the the general reason for getting this
> > msg. BUT what we are surprised is that this works great
> > in Sybase & for some reason fails in MS_SQL Server. I
> > know for sure that I am the only one accessing this data
> > so there is no reason for getting the "ROW CHANGED.."
> > error. The DW has of course 'key & updateable columns' &
> > if we change to 'key columns' this might work in MS-SQL.
> > BUT want to know what could be the cause for this to
> > fail in MS-SQL. Has anybody else experienced this when
> > migrating from Sybase to MS-SQL Server2008
> > Thnx
> > Anil
>
>

This worked too. Thanks a lot.
So which is a better option. RecheckRows or setting NOCOUNT
ON in the trigger?
I have'nt understood how  NOCOUNT ON will resolve the issue.
Pl. advice about this.
THnx
Anil

> In addition to what Chris said you may want to look at the
> RecheckRows dbparm.
>
>
> > Hi Anil;
> >
> >   Sorry to hear that you have had to downgrade your
> > DBMS! :-))))
> >
> > I suspect that changing the DW update to Key only will
> > be the ticket. I  think the problem might be due to
> > checking the updatable columns where maybe  the DBA has
> > added a trigger that is updating something, changed a
> > data type thus the columns behaviour, etc.
> >
> > HTH
> >
> > Regards ... Chris
> > President: OSUG / STD Inc.
> > Blog: http://chrispollach.blogspot.com
> > PBDJ: http://chrispollach.sys-con.com
> > SourceForge: http://sourceforge.net/projects/stdfndclass
> >
> > "anil" wrote in message
> > news:4cf86867.775f.1681692777@sybase.com...
> >
> > We are currently migrating our app from SYbase to MS-SQL
> > Server 2008. We are using PB11.5 & connecting to MS-SQL
> > Server using the PB Native Driver (SQLNCLI10).
> >
> > In one of the windows we are getting "Row changed
> > between Retrieve & Update". Can anybody give a clue why
> > this might be happening.
> >
> > The window works perfectly in SybaseBUT is failing in
> > MS_SQL.I know the the general reason for getting this
> > msg. BUT what we are surprised is that this works great
> > in Sybase & for some reason fails in MS_SQL Server. I
> > know for sure that I am the only one accessing this data
> > so there is no reason for getting the "ROW CHANGED.."
> > error. The DW has of course 'key & updateable columns' &
> > if we change to 'key columns' this might work in MS-SQL.
> > BUT want to know what could be the cause for this to
> > fail in MS-SQL. Has anybody else experienced this when
> > migrating from Sybase to MS-SQL Server2008
> > Thnx
> > Anil
> >

Yes, its pretty much the same direction here in the Canadian federal 
government.   :-(

I think it was Ted that was talking about the Set options.


"Anil" wrote in message news:4cfa47a9.43b4.1681692777@sybase.com...

Hi Chris,
I would partly blame this on Sybase too. We have been
migrating our app. for the last 2 months & with my 'limited'
experience of using ms-sql during this short period, I am
actually seeing some pretty strong reasons for taking a
stand on MS_SQL Server.

The sad thing is our mgmt were also seriously thinking of
replacing PB with C# BUT due to the huge size of our app.,
risk & the budget to convert to C#, we are now thinking of
having a mix of PB & C# wen we migrate to PB12.NET.
Eventually a day will come soon when our app. will be
replaced by C#. This will be the saddest day of my
professional life.

Anyway, Chris - Pl. advice as to how SET NOCOUNT ON  can fix
the issue.

Thnx
Anil
> Hi Anil;
>
>    Pretty much the same here in Canada's capital. Most ASE
> shops have now  switched to SS due to management pressure.
>  :-(
>
>
> Regards ... Chris
> President: OSUG / STD Inc.
> Blog: http://chrispollach.blogspot.com
> PBDJ: http://chrispollach.sys-con.com
> SourceForge: http://sourceforge.net/projects/stdfndclass
>
> "Anil" wrote in message
> news:4cf9733b.2473.1681692777@sybase.com...
>
> Hello Chris
> Yes. Its unfortunate that we are forced to downgrade. Been
> working in Sybase for the last 15 years. Blame it on Mgmt.
> :(
>
> I was researching on this issue &found a link where Bruce
> Armstrong had suggested to put SET NOCOUNT ON in the
> trigger. Adding this, my data is saving & I am not getting
> any error. But I am not understanding how NOCOUNT ON can
> resolve this problem. I am just worried if this is the
> correct solution OR this is just masking the error.
> How can SET NOCOUNT ON mask this error & is this the
> correct solution?
> Anil
>
> > Hi Anil;
> >
> >   Sorry to hear that you have had to downgrade your
> > DBMS! :-))))
> >
> > I suspect that changing the DW update to Key only will
> > be the ticket. I  think the problem might be due to
> > checking the updatable columns where maybe  the DBA has
> > added a trigger that is updating something, changed a
> > data type thus the columns behaviour, etc.
> >
> > HTH
> >
> > Regards ... Chris
> > President: OSUG / STD Inc.
> > Blog: http://chrispollach.blogspot.com
> > PBDJ: http://chrispollach.sys-con.com
> > SourceForge: http://sourceforge.net/projects/stdfndclass
> >
> > "anil" wrote in message
> > news:4cf86867.775f.1681692777@sybase.com...
> >
> > We are currently migrating our app from SYbase to MS-SQL
> > Server 2008. We are using PB11.5 & connecting to MS-SQL
> > Server using the PB Native Driver (SQLNCLI10).
> >
> > In one of the windows we are getting "Row changed
> > between Retrieve & Update". Can anybody give a clue why
> > this might be happening.
> >
> > The window works perfectly in SybaseBUT is failing in
> > MS_SQL.I know the the general reason for getting this
> > msg. BUT what we are surprised is that this works great
> > in Sybase & for some reason fails in MS_SQL Server. I
> > know for sure that I am the only one accessing this data
> > so there is no reason for getting the "ROW CHANGED.."
> > error. The DW has of course 'key & updateable columns' &
> > if we change to 'key columns' this might work in MS-SQL.
> > BUT want to know what could be the cause for this to
> > fail in MS-SQL. Has anybody else experienced this when
> > migrating from Sybase to MS-SQL Server2008
> > Thnx
> > Anil
> >
> 

I mentioned to check the RecheckRows dbparm in the
Powerbuilder help.

Rechecks the number of rows affected by an INSERT, UPDATE,
or DELETE command and returns it in the SQLNRows property of
the Transaction object.

In Microsoft SQL server, if a table has an insert, update,
or delete trigger, the number of affected rows returned to
the SQLNRows property of the Transaction object after an
INSERT, UPDATE, or DELETE command depends on the driver...

> Yes, its pretty much the same direction here in the
> Canadian federal  government.   :-(
>
> I think it was Ted that was talking about the Set options.
>
>
> "Anil" wrote in message
> news:4cfa47a9.43b4.1681692777@sybase.com...
>
> Hi Chris,
> I would partly blame this on Sybase too. We have been
> migrating our app. for the last 2 months & with my
> 'limited' experience of using ms-sql during this short
> period, I am actually seeing some pretty strong reasons
> for taking a stand on MS_SQL Server.
>
> The sad thing is our mgmt were also seriously thinking of
> replacing PB with C# BUT due to the huge size of our app.,
> risk & the budget to convert to C#, we are now thinking of
> having a mix of PB & C# wen we migrate to PB12.NET.
> Eventually a day will come soon when our app. will be
> replaced by C#. This will be the saddest day of my
> professional life.
>
> Anyway, Chris - Pl. advice as to how SET NOCOUNT ON  can
> fix the issue.
>
> Thnx
> Anil
> > Hi Anil;
> >
> >    Pretty much the same here in Canada's capital. Most
> > ASE shops have now  switched to SS due to management
> >  pressure. :-(
> >
> >
> > Regards ... Chris
> > President: OSUG / STD Inc.
> > Blog: http://chrispollach.blogspot.com
> > PBDJ: http://chrispollach.sys-con.com
> > SourceForge: http://sourceforge.net/projects/stdfndclass
> >
> > "Anil" wrote in message
> > news:4cf9733b.2473.1681692777@sybase.com...
> >
> > Hello Chris
> > Yes. Its unfortunate that we are forced to downgrade.
> > Been working in Sybase for the last 15 years. Blame it
> > on Mgmt. :(
> >
> > I was researching on this issue &found a link where
> > Bruce Armstrong had suggested to put SET NOCOUNT ON in
> > the trigger. Adding this, my data is saving & I am not
> > getting any error. But I am not understanding how
> > NOCOUNT ON can resolve this problem. I am just worried
> > if this is the correct solution OR this is just masking
> > the error. How can SET NOCOUNT ON mask this error & is
> > this the correct solution?
> > Anil
> >
> > > Hi Anil;
> > >
> > >   Sorry to hear that you have had to downgrade your
> > > DBMS! :-))))
> > >
> > > I suspect that changing the DW update to Key only will
> > > be the ticket. I  think the problem might be due to
> > > checking the updatable columns where maybe  the DBA
> > > has added a trigger that is updating something,
> > > changed a data type thus the columns behaviour, etc.
> > >
> > > HTH
> > >
> > > Regards ... Chris
> > > President: OSUG / STD Inc.
> > > Blog: http://chrispollach.blogspot.com
> > > PBDJ: http://chrispollach.sys-con.com
> > > SourceForge:
> > http://sourceforge.net/projects/stdfndclass >
> > > "anil" wrote in message
> > > news:4cf86867.775f.1681692777@sybase.com...
> > >
> > > We are currently migrating our app from SYbase to
> > > MS-SQL Server 2008. We are using PB11.5 & connecting
> > > to MS-SQL Server using the PB Native Driver
> > (SQLNCLI10). >
> > > In one of the windows we are getting "Row changed
> > > between Retrieve & Update". Can anybody give a clue
> > > why this might be happening.
> > >
> > > The window works perfectly in SybaseBUT is failing in
> > > MS_SQL.I know the the general reason for getting this
> > > msg. BUT what we are surprised is that this works
> > > great in Sybase & for some reason fails in MS_SQL
> > > Server. I know for sure that I am the only one
> > > accessing this data so there is no reason for getting
> > > the "ROW CHANGED.." error. The DW has of course 'key &
> > > updateable columns' & if we change to 'key columns'
> > > this might work in MS-SQL. BUT want to know what could
> > > be the cause for this to fail in MS-SQL. Has anybody
> > > else experienced this when migrating from Sybase to
> > > MS-SQL Server2008 Thnx
> > > Anil
> > >
> >
>

Does your data use char types?  If so, you might get hit by trimming of 
traling spaces.  From the online help for the trimspaces dbparm:

>>By default, PowerBuilder trims spaces from the following datatypes: Char, 
>>Char for Bit Data, VarChar, and VarChar for Bit Data.
ODBC database interface    Some ODBC drivers, such as ASA, trim trailing 
spaces before the data reaches the fetch buffer—even when TrimSpaces is set 
to 0.
If your DBMS makes a distinction between Char data with trailing spaces and 
Char data without trailing spaces when evaluating a WHERE clause expression, 
you might receive the message Row changed between retrieve and update when 
your DataWindow update properties are set to "Key and updateable columns." 
To prevent this, change your DataWindow update properties. In embedded SQL, 
you can check Sqlca.Sqlnrows after each update to determine if the update 
took place. Avoid using Char data columns in the WHERE clause of an UPDATE 
or DELETE statement when TrimSpaces=1.<<

-- Terry Dykstra (TeamSybase)
http://powerbuilder.codeXchange.sybase.com/
http://casexpress.sybase.com
http://my.isug.com/cgi-bin/1/c/submit_enhancement

"Ted Zimmerman [Sybase]" wrote in message 
news:4cfd24cf.206b.1681692777@sybase.com...

I mentioned to check the RecheckRows dbparm in the
Powerbuilder help.

Rechecks the number of rows affected by an INSERT, UPDATE,
or DELETE command and returns it in the SQLNRows property of
the Transaction object.

In Microsoft SQL server, if a table has an insert, update,
or delete trigger, the number of affected rows returned to
the SQLNRows property of the Transaction object after an
INSERT, UPDATE, or DELETE command depends on the driver...

> Yes, its pretty much the same direction here in the
> Canadian federal  government.   :-(
>
> I think it was Ted that was talking about the Set options.
>
>
> "Anil" wrote in message
> news:4cfa47a9.43b4.1681692777@sybase.com...
>
> Hi Chris,
> I would partly blame this on Sybase too. We have been
> migrating our app. for the last 2 months & with my
> 'limited' experience of using ms-sql during this short
> period, I am actually seeing some pretty strong reasons
> for taking a stand on MS_SQL Server.
>
> The sad thing is our mgmt were also seriously thinking of
> replacing PB with C# BUT due to the huge size of our app.,
> risk & the budget to convert to C#, we are now thinking of
> having a mix of PB & C# wen we migrate to PB12.NET.
> Eventually a day will come soon when our app. will be
> replaced by C#. This will be the saddest day of my
> professional life.
>
> Anyway, Chris - Pl. advice as to how SET NOCOUNT ON  can
> fix the issue.
>
> Thnx
> Anil
> > Hi Anil;
> >
> >    Pretty much the same here in Canada's capital. Most
> > ASE shops have now  switched to SS due to management
> >  pressure. :-(
> >
> >
> > Regards ... Chris
> > President: OSUG / STD Inc.
> > Blog: http://chrispollach.blogspot.com
> > PBDJ: http://chrispollach.sys-con.com
> > SourceForge: http://sourceforge.net/projects/stdfndclass
> >
> > "Anil" wrote in message
> > news:4cf9733b.2473.1681692777@sybase.com...
> >
> > Hello Chris
> > Yes. Its unfortunate that we are forced to downgrade.
> > Been working in Sybase for the last 15 years. Blame it
> > on Mgmt. :(
> >
> > I was researching on this issue &found a link where
> > Bruce Armstrong had suggested to put SET NOCOUNT ON in
> > the trigger. Adding this, my data is saving & I am not
> > getting any error. But I am not understanding how
> > NOCOUNT ON can resolve this problem. I am just worried
> > if this is the correct solution OR this is just masking
> > the error. How can SET NOCOUNT ON mask this error & is
> > this the correct solution?
> > Anil
> >
> > > Hi Anil;
> > >
> > >   Sorry to hear that you have had to downgrade your
> > > DBMS! :-))))
> > >
> > > I suspect that changing the DW update to Key only will
> > > be the ticket. I  think the problem might be due to
> > > checking the updatable columns where maybe  the DBA
> > > has added a trigger that is updating something,
> > > changed a data type thus the columns behaviour, etc.
> > >
> > > HTH
> > >
> > > Regards ... Chris
> > > President: OSUG / STD Inc.
> > > Blog: http://chrispollach.blogspot.com
> > > PBDJ: http://chrispollach.sys-con.com
> > > SourceForge:
> > http://sourceforge.net/projects/stdfndclass >
> > > "anil" wrote in message
> > > news:4cf86867.775f.1681692777@sybase.com...
> > >
> > > We are currently migrating our app from SYbase to
> > > MS-SQL Server 2008. We are using PB11.5 & connecting
> > > to MS-SQL Server using the PB Native Driver
> > (SQLNCLI10). >
> > > In one of the windows we are getting "Row changed
> > > between Retrieve & Update". Can anybody give a clue
> > > why this might be happening.
> > >
> > > The window works perfectly in SybaseBUT is failing in
> > > MS_SQL.I know the the general reason for getting this
> > > msg. BUT what we are surprised is that this works
> > > great in Sybase & for some reason fails in MS_SQL
> > > Server. I know for sure that I am the only one
> > > accessing this data so there is no reason for getting
> > > the "ROW CHANGED.." error. The DW has of course 'key &
> > > updateable columns' & if we change to 'key columns'
> > > this might work in MS-SQL. BUT want to know what could
> > > be the cause for this to fail in MS-SQL. Has anybody
> > > else experienced this when migrating from Sybase to
> > > MS-SQL Server2008 Thnx
> > > Anil
> > >
> >
>