I found an old post by Stephen Dupre / Simon Caldwell ;
http://groups.google.be/group/powersoft.public.powerbuilder.datawindow/browse_thread/thread/4aff464c82317017/33ca3127bf361ef2?lnk=st&q=update+properties+modified+updateable&rnum=6&hl=fr#33ca3127bf361ef2
dated 1998 where a similar problem is shown.
Is this fixed ? or will it be ?
Extract of the old post
From: "Simon Caldwell" Subject: Re: Key and Modified Columns Bug
Date: 1998/08/27
Why can't the functionality be changed then? Surely it shouldn't be too
hard to add a 'key and modified updateable columns' option?
Simon
Stephen Dupre[Sybase] wrote in message
>This is a bad GUI problem but not a bug. For Rows/Update specifications
>we left this as a feature (the ability to generate something in the
>where clause for ANY column that's modified - even a named computed
>column). The problem is the UI (selected columns in the listbox)
>doesn't reflect the where clause than can be generated.
>
>I tried to get development to change the UI for 5.0 - basically when the
>user clicks "key and modified" to 'grey out' the listbox so it's clear
>that nothing the developer selected there matters now - only that
>whatever columns are left open and editable will end up in the where
>clause if modified. It's up to the developer to make sure this doesn't
>happen through PowerScript.
>
>Maybe we'll try again for the next version of PB to change the UI (but
>not the functionality). It's definitely confusing.
>
>Stephen Dupre
>Sybase