The db trace reveals nothing, and no database error conditions are evoked,
leading me to believe that the update is never even attempted. I
experienced a similar problem with simple datastores using stored
procedures, where the - 1 was returned before the SQLPreview event was
triggered, let alone the DBError. A call to Sybase technical support never
resolved the problem.
If anyone has experienced similar behavior, and has a resolution, please let
me know. I've tried everything else I could think of to the point where I
am considering re-retrieving the data. This is not an optimum business
solution as other updates not yet commited would be lost.
Thanks in advance.
>I am having trouble executing the ReselectRow() function to cancel updates
>in a datawindow with updates allowed. I have observed execution in the
>debugger, and the function returns a -1. I am using PB v.6.0. The data
>source for the datawindow is an Oracle stored procedure (v. 7.3).
Consider what ReselectRow ( ) does. It takes the UpdateTable, all the Updateable
Columns and the values for any columns identified in the Unique Key Columns from
the datawindow object and generates a one-off SQL SELECT statement. Typically
when you use a stored procedure as a data source there is no updateable table
because your data source is a stored procedure. That would be my guess anyway.
---
Craig Wagner | E-mail: cwa...@metacorp.com
CPD Professional | Web: http://www.metacorp.com
Certified Powersoft Instructor | Phone: (503) 452-6343
Portland, OR USA |
Keeper of the PowerBuilder FAQ
http://www.teleport.com/~wagnerc/powerbuilder_faq.html
I'm not sure about Oracle, but in my experience with Sybase, you have to include
the timestamp column in the SQL query in order to get the ReselectRow to work.
Without the timestamp column, PB cannot determine if the row has changed between
selects.You might already know this, but you didn't mention timestamps in your
post.
HTH
Douglas Woods wrote:
> I am having trouble executing the ReselectRow() function to cancel updates
> in a datawindow with updates allowed. I have observed execution in the
> debugger, and the function returns a -1. I am using PB v.6.0. The data
> source for the datawindow is an Oracle stored procedure (v. 7.3).
>