PowerBuilder won't reactivate License after update. When I ran Powerbuilder. I then went to the SAP site and regenerated a new license key for my. SQL UPDATE Statement Hangs Powerbuilder. Statement in my code that hangs Powerbuilder 12.5. UPDATE COMMENTS SET. Logging in place and find out if it is. Hi, I've a strange problem with a datastore which is controlled by a PFC like update service. All updateable datastores and datawindows have to h.

1. Slimware Driver Update Key
2. Update Key West Hurricane Recovery Images

Newsgroups: sybase.public.powerbuilder.database Date: Fri, 27 Mar 1998 16:23:03 -0800 From: 'Sean A. O'Keefe' X-Mailer: Mozilla 4.04 en (WinNT; U) MIME-Version: 1.0 Subject: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 13 Message-ID: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com Xref: forums-1-dub sybase.public.powerbuilder.database:17601 Article PK: 314803. Newsgroups: sybase.public.powerbuilder.database Date: Mon, 30 Mar 1998 19:37:05 -0800 From: Stephen Dupre Reply-To: sdupre@powersoft.com Organization: Powersoft Tools, Sybase, Inc. X-Mailer: Mozilla 3.0 (Win16; U) MIME-Version: 1.0 To: 'Sean A.

O'Keefe' Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 25 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com Xref: forums-1-dub sybase.public.powerbuilder.database:17586 Article PK: 314786. O'Keefe wrote: I was under the mistaken impression that Key & Modified would be a subset of the Key & Updateable columns. The PB help seems very fuzzy on this point. Basically we put columns on our datawindows for the surogate key to be entered, then we map the real key into another column using an nvo. The problem is the surogate column is now modified and ends up in the where clause for updates and deletes. This seems like a bug to me, I thought I would ask here before contacting PB support. This is not a bug.

It's a feature of 'Key and Modified' to allow other columns to be included and some developers take advantage of this. If you use this option, we assume you know what you're doing with regards to the where clause. I lobbied for a messagebox warning the user that this is an advanced option but was shot down. It should be in the documentation (at least in the printed). Stephen Dupre Sybase. Newsgroups: sybase.public.powerbuilder.database Date: Wed, 01 Apr 1998 09:08:37 -0800 From: 'Sean A.

O'Keefe' X-Mailer: Mozilla 4.04 en (WinNT; U) MIME-Version: 1.0 Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 19 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com Xref: forums-1-dub sybase.public.powerbuilder.database:17567 Article PK: 314770. The documentation talks about Key and Modified as increasing concurrency.

No where does it discuss this as being an advanced feature. How do 'some developers take advantage of this'? Can you provide some valid use-cases for this? We'd really like to know. Stephen Dupre wrote: This is not a bug. It's a feature of 'Key and Modified' to allow other columns to be included and some developers take advantage of this. If you use this option, we assume you know what you're doing with regards to the where clause.

I lobbied for a messagebox warning the user that this is an advanced option but was shot down. It should be in the documentation (at least in the printed). Stephen Dupre Sybase. Newsgroups: sybase.public.powerbuilder.database Date: Fri, 10 Apr 1998 19:44:10 +0530 From: Mohan Patil X-Mailer: Mozilla 3.01 (Win95; I) MIME-Version: 1.0 Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 14 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com Xref: forums-1-dub sybase.public.powerbuilder.database:17475 Article PK: 314680. Hi Stephen, Will you please explane how it is advantageous.

Stephen Dupre wrote: This is not a bug. It's a feature of 'Key and Modified' to allow other columns to be included and some developers take advantage of this. If you use this option, we assume you know what you're doing with regards to the where clause.

I lobbied for a messagebox warning the user that this is an advanced option but was shot down. It should be in the documentation (at least in the printed). Stephen Dupre Sybase.

Newsgroups: sybase.public.powerbuilder.database Date: Thu, 02 Apr 1998 18:32:47 -0800 From: Stephen Dupre Reply-To: Stephen.Dupre@sybase.com Organization: Powersoft Tools Division, Sybase, Inc. X-Mailer: Mozilla 3.0 (Win16; U) MIME-Version: 1.0 Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 43 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com Xref: forums-1-dub sybase.public.powerbuilder.database:17535 Article PK: 314738. O'Keefe wrote: The documentation talks about Key and Modified as increasing concurrency. No where does it discuss this as being an advanced feature. How do 'some developers take advantage of this'?

Can you provide some valid use-cases for this? We'd really like to know. Stephen Dupre wrote: This is not a bug.

It's a feature of 'Key and Modified' to allow other columns to be included and some developers take advantage of this. If you use this option, we assume you know what you're doing with regards to the where clause. I lobbied for a messagebox warning the user that this is an advanced option but was shot down. It should be in the documentation (at least in the printed). Stephen Dupre Sybase 'Key and modified' is really 'unlinked' from the 'updateable columns' list. It will put in the WHERE clause ANY column that is modified (computed columns too or columns from tables not currently pointed to by the 'table to update' property.) whether it's highlighted or not in the listbox.

It's not clear from the GUI that this is so. I lobbied for having the 'updateable columns' listbox grey out when 'key and modified' is checked to make this more clear but it did not get into the product. That means you have to be very aware of columns you leave open for input with tab order, etc when you use 'key and modified'.

With Key and updateable, it's different since it only affects columns highlighted in the 'updateable columns' listbox. I can't think of an application but we did have a large customer that wanted it to stay this way. Stephen Dupre Sybase.

Newsgroups: sybase.public.powerbuilder.database Date: Mon, 03 May 1999 13:22:12 -0700 From: 'Steven D. Kincer' X-Mailer: Mozilla 4.5 en (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 CC: rongallagher@mindspring.com, Stephen.Dupre@sybase.com Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 58 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com Xref: forums-1-dub sybase.public.powerbuilder.database:13523 Article PK: 305920. Stephen Dupre wrote: Sean A. O'Keefe wrote: The documentation talks about Key and Modified as increasing concurrency. No where does it discuss this as being an advanced feature.

How do 'some developers take advantage of this'? Can you provide some valid use-cases for this? We'd really like to know. Stephen Dupre wrote: This is not a bug.

It's a feature of 'Key and Modified' to allow other columns to be included and some developers take advantage of this. If you use this option, we assume you know what you're doing with regards to the where clause. I lobbied for a messagebox warning the user that this is an advanced option but was shot down. It should be in the documentation (at least in the printed).

Stephen Dupre Sybase 'Key and modified' is really 'unlinked' from the 'updateable columns' list. It will put in the WHERE clause ANY column that is modified (computed columns too or columns from tables not currently pointed to by the 'table to update' property.) whether it's highlighted or not in the listbox.

It's not clear from the GUI that this is so. I lobbied for having the 'updateable columns' listbox grey out when 'key and modified' is checked to make this more clear but it did not get into the product. That means you have to be very aware of columns you leave open for input with tab order, etc when you use 'key and modified'. With Key and updateable, it's different since it only affects columns highlighted in the 'updateable columns' listbox.

I can't think of an application but we did have a large customer that wanted it to stay this way. Stephen Dupre Sybase Stephen: Unless I'm misunderstanding one of you, the following paragraph.' In the third test, I removed colc from the 'updateable columns' list. When I ran the app, regardless of the changes I made to col c or how I set the where clause, colc was never included in a where clause.' From Ron Gallagher's post (from 3/30/98) is in direct conflict with yours.

Am I missing something? Thanks, and if you could copy any reply to my email I'd appreciate it.

Steve Kincer (sxk@proc2000.sannet.gov) cc: Stephen, Ron. Newsgroups: sybase.public.powerbuilder.database Date: Mon, 03 May 1999 13:21:22 -0700 From: 'Steven D. Kincer' X-Mailer: Mozilla 4.5 en (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 CC: rongallagher@mindspring.com, Stephen.Dupre@sybase.com Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 58 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com Xref: forums-1-dub sybase.public.powerbuilder.database:13524 Article PK: 305921.

Stephen Dupre wrote: Sean A. O'Keefe wrote: The documentation talks about Key and Modified as increasing concurrency. No where does it discuss this as being an advanced feature. How do 'some developers take advantage of this'? Can you provide some valid use-cases for this? We'd really like to know. Stephen Dupre wrote: This is not a bug.

It's a feature of 'Key and Modified' to allow other columns to be included and some developers take advantage of this. If you use this option, we assume you know what you're doing with regards to the where clause. I lobbied for a messagebox warning the user that this is an advanced option but was shot down.

It should be in the documentation (at least in the printed). Stephen Dupre Sybase 'Key and modified' is really 'unlinked' from the 'updateable columns' list. It will put in the WHERE clause ANY column that is modified (computed columns too or columns from tables not currently pointed to by the 'table to update' property.) whether it's highlighted or not in the listbox. It's not clear from the GUI that this is so.

I lobbied for having the 'updateable columns' listbox grey out when 'key and modified' is checked to make this more clear but it did not get into the product. That means you have to be very aware of columns you leave open for input with tab order, etc when you use 'key and modified'. With Key and updateable, it's different since it only affects columns highlighted in the 'updateable columns' listbox. I can't think of an application but we did have a large customer that wanted it to stay this way.

Stephen Dupre Sybase Stephen: Unless I'm misunderstanding one of you, the following paragraph.' In the third test, I removed colc from the 'updateable columns' list. When I ran the app, regardless of the changes I made to col c or how I set the where clause, colc was never included in a where clause.' From Ron Gallagher's post (from 3/30/98) is in direct conflict with yours. Am I missing something? Thanks, and if you could copy any reply to my email I'd appreciate it.

Steve Kincer (sxk@proc2000.sannet.gov) cc: Stephen, Ron. Newsgroups: sybase.public.powerbuilder.database Date: Mon, 03 May 1999 13:20:15 -0700 From: 'Steven D. Kincer' X-Mailer: Mozilla 4.5 en (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 CC: rongallagher@mindspring.com, Stephen.Dupre@sybase.com Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 58 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com Xref: forums-1-dub sybase.public.powerbuilder.database:13525 Article PK: 305922.

Stephen Dupre wrote: Sean A. O'Keefe wrote: The documentation talks about Key and Modified as increasing concurrency. No where does it discuss this as being an advanced feature. How do 'some developers take advantage of this'? Can you provide some valid use-cases for this? We'd really like to know. Stephen Dupre wrote: This is not a bug.

It's a feature of 'Key and Modified' to allow other columns to be included and some developers take advantage of this. If you use this option, we assume you know what you're doing with regards to the where clause. I lobbied for a messagebox warning the user that this is an advanced option but was shot down. It should be in the documentation (at least in the printed).

Stephen Dupre Sybase 'Key and modified' is really 'unlinked' from the 'updateable columns' list. It will put in the WHERE clause ANY column that is modified (computed columns too or columns from tables not currently pointed to by the 'table to update' property.) whether it's highlighted or not in the listbox. It's not clear from the GUI that this is so. I lobbied for having the 'updateable columns' listbox grey out when 'key and modified' is checked to make this more clear but it did not get into the product. That means you have to be very aware of columns you leave open for input with tab order, etc when you use 'key and modified'.

With Key and updateable, it's different since it only affects columns highlighted in the 'updateable columns' listbox. I can't think of an application but we did have a large customer that wanted it to stay this way. Stephen Dupre Sybase Stephen: Unless I'm misunderstanding one of you, the following paragraph.'

In the third test, I removed colc from the 'updateable columns' list. When I ran the app, regardless of the changes I made to col c or how I set the where clause, colc was never included in a where clause.' From Ron Gallagher's post (from 3/30/98) is in direct conflict with yours. Am I missing something?

Thanks, and if you could copy any reply to my email I'd appreciate it. Steve Kincer (sxk@proc2000.sannet.gov) cc: Stephen, Ron.

Newsgroups: sybase.public.powerbuilder.database Date: Mon, 03 May 1999 13:19:20 -0700 From: 'Steven D. Kincer' X-Mailer: Mozilla 4.5 en (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 CC: rongallagher@mindspring.com, Stephen.Dupre@sybase.com Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 58 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com Xref: forums-1-dub sybase.public.powerbuilder.database:13526 Article PK: 305923. Stephen Dupre wrote: Sean A. O'Keefe wrote: The documentation talks about Key and Modified as increasing concurrency.

No where does it discuss this as being an advanced feature. How do 'some developers take advantage of this'? Can you provide some valid use-cases for this? We'd really like to know.

Stephen Dupre wrote: This is not a bug. It's a feature of 'Key and Modified' to allow other columns to be included and some developers take advantage of this. If you use this option, we assume you know what you're doing with regards to the where clause. I lobbied for a messagebox warning the user that this is an advanced option but was shot down.

It should be in the documentation (at least in the printed). Stephen Dupre Sybase 'Key and modified' is really 'unlinked' from the 'updateable columns' list.

It will put in the WHERE clause ANY column that is modified (computed columns too or columns from tables not currently pointed to by the 'table to update' property.) whether it's highlighted or not in the listbox. It's not clear from the GUI that this is so. I lobbied for having the 'updateable columns' listbox grey out when 'key and modified' is checked to make this more clear but it did not get into the product. That means you have to be very aware of columns you leave open for input with tab order, etc when you use 'key and modified'. With Key and updateable, it's different since it only affects columns highlighted in the 'updateable columns' listbox. I can't think of an application but we did have a large customer that wanted it to stay this way.

Stephen Dupre Sybase Stephen: Unless I'm misunderstanding one of you, the following paragraph.' In the third test, I removed colc from the 'updateable columns' list. When I ran the app, regardless of the changes I made to col c or how I set the where clause, colc was never included in a where clause.' From Ron Gallagher's post (from 3/30/98) is in direct conflict with yours.

Am I missing something? Thanks, and if you could copy any reply to my email I'd appreciate it.

Steve Kincer (sxk@proc2000.sannet.gov) cc: Stephen, Ron. Newsgroups: sybase.public.powerbuilder.database Date: Mon, 03 May 1999 13:12:51 -0700 From: 'Steven D. Kincer' X-Mailer: Mozilla 4.5 en (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 CC: rongallagher@mindspring.com, Stephen.Dupre@sybase.com Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 58 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com Xref: forums-1-dub sybase.public.powerbuilder.database:13527 Article PK: 305924. Stephen Dupre wrote: Sean A.

O'Keefe wrote: The documentation talks about Key and Modified as increasing concurrency. No where does it discuss this as being an advanced feature. How do 'some developers take advantage of this'? Can you provide some valid use-cases for this? We'd really like to know.

Stephen Dupre wrote: This is not a bug. It's a feature of 'Key and Modified' to allow other columns to be included and some developers take advantage of this. If you use this option, we assume you know what you're doing with regards to the where clause. I lobbied for a messagebox warning the user that this is an advanced option but was shot down. It should be in the documentation (at least in the printed). Stephen Dupre Sybase 'Key and modified' is really 'unlinked' from the 'updateable columns' list. It will put in the WHERE clause ANY column that is modified (computed columns too or columns from tables not currently pointed to by the 'table to update' property.) whether it's highlighted or not in the listbox.

It's not clear from the GUI that this is so. I lobbied for having the 'updateable columns' listbox grey out when 'key and modified' is checked to make this more clear but it did not get into the product. That means you have to be very aware of columns you leave open for input with tab order, etc when you use 'key and modified'. With Key and updateable, it's different since it only affects columns highlighted in the 'updateable columns' listbox. I can't think of an application but we did have a large customer that wanted it to stay this way. Stephen Dupre Sybase Stephen: Unless I'm misunderstanding one of you, the following paragraph.'

In the third test, I removed colc from the 'updateable columns' list. When I ran the app, regardless of the changes I made to col c or how I set the where clause, colc was never included in a where clause.'

From Ron Gallagher's post (from 3/30/98) is in direct conflict with yours. Am I missing something? Thanks, and if you could copy any reply to my email I'd appreciate it. Steve Kincer (sxk@proc2000.sannet.gov) cc: Stephen, Ron.

Newsgroups: sybase.public.powerbuilder.database From: 'Paul A. Horan' Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Date: Wed, 1 Apr 1998 15:30:40 -0500 Lines: 47 Organization: VCI X-Newsreader: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com Xref: forums-1-dub sybase.public.powerbuilder.database:17555 Article PK: 314760. Sean, PMFJI, this feature is used when several users may be updating the same row, and possibly the same columns, at the same time. Let's say that User A has the authority to update Salary information, and User B has the authority to update Address info, and they're both looking at the same row in the Employee table at the same time. User A changes the salary, and User B changes the Zip Code, and they both press OK simultaneously. Using Key and Updateable will cause User B's update to fail, because the Salary info that User A changed would no longer match the Where clause that User B would generate.

Using Key and Modified would allow both updates to proceed, because the non-modified columns are not in the respective Where clauses. Using Key only would have allowed both updates to proceed as well, however, in the case where two users are updating the same non-key column on the same row, there would be no way to stop User A's changes from being overwritten by User B's update. Paul Horan VCI Springfield, MA Sean A. O'Keefe wrote in message. The documentation talks about Key and Modified as increasing concurrency. No where does it discuss this as being an advanced feature.

How do 'some developers take advantage of this'? Can you provide some valid use-cases for this? We'd really like to know. Stephen Dupre wrote: This is not a bug. It's a feature of 'Key and Modified' to allow other columns to be included and some developers take advantage of this. If you use this option, we assume you know what you're doing with regards to the where clause. I lobbied for a messagebox warning the user that this is an advanced option but was shot down.

It should be in the documentation (at least in the printed). Stephen Dupre Sybase. Newsgroups: sybase.public.powerbuilder.database Date: Mon, 30 Mar 1998 11:23:18 -0500 From: Ron Gallagher Reply-To: rongallagher@mindspring.com Organization: RGI X-Mailer: Mozilla 3.01 (WinNT; I) MIME-Version: 1.0 Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 42 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com Xref: forums-1-dub sybase.public.powerbuilder.database:17592 Article PK: 314795. Sean - You are correct. Key & Modifed is a subset of Key and Updateable. Two statements that you make stand out: 1) 'we put columns on our datawindows for the surogate key to be entered' 2) 'the surogate column is now modified and ends up in the where clause for updates and deletes' Based on the first statement, I'm assuming that your users are entering the values into the surrogate key columns. Since users are modifying these columns, then these columns will always be included in the where clause of any update/delete statement generated by the DW whenever the Where clause option is 'Key & Modifed' or 'Key and Updateable'.

To keep this from happening, you have two options: 1) Access the Rows Update Properties menu option change the Where clause to Key Columns only. 2) Access the Rows Update Properties menu option and remove the surrogate key columns from the list of columns that can be updated.

Keep in mind that if you do this, no changes to these columns will be reflected in your database. HTH Ron Gallagher, CPDP Atlanta, GA, USA rongallagher@mindspring.com Sean A. O'Keefe wrote: I was under the mistaken impression that Key & Modified would be a subset of the Key & Updateable columns. The PB help seems very fuzzy on this point. Basically we put columns on our datawindows for the surogate key to be entered, then we map the real key into another column using an nvo. The problem is the surogate column is now modified and ends up in the where clause for updates and deletes. This seems like a bug to me, I thought I would ask here before contacting PB support.

Newsgroups: sybase.public.powerbuilder.database Date: Mon, 30 Mar 1998 13:40:20 -0800 From: 'Sean A. O'Keefe' X-Mailer: Mozilla 4.04 en (WinNT; U) MIME-Version: 1.0 Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 27 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com Xref: forums-1-dub sybase.public.powerbuilder.database:17589 Article PK: 314789. Let me try and clarify our situation a little more. I believe that PB's standard way of doing what we are trying to do is to place a Drop Down DataWindow on the DataWindow. In our case the Surrogate Key would be the display value while the actual key would be the data value; however we are dealing with long lists that do not lend themselves to dddw's.

We paint both these columns on the datawindow and then have the nvo copy in the key column value after the user enters the surrogate key. While both columns are modified, only the actual key column is in the list of updateable columns. When 'Key and Modified' is selected, then both columns appear in the where clause, this fails because in our case the surogate key is not in the table we are trying to update.

When 'Key and Updateable' is selected then only the actual key column appears in the Where clause. This leads me to believe that 'Key and Modified' does not look at the Upadatable Columns list when formulating the Where clause. Is this a bug, or is it what PB intended? Newsgroups: sybase.public.powerbuilder.database Date: Mon, 30 Mar 1998 13:37:43 -0800 From: 'Sean A. O'Keefe' X-Mailer: Mozilla 4.04 en (WinNT; U) MIME-Version: 1.0 To: rongallagher@mindspring.com Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 27 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com Xref: forums-1-dub sybase.public.powerbuilder.database:17590 Article PK: 314792. Let me try and clarify our situation a little more. I believe that PB's standard way of doing what we are trying to do is to place a Drop Down DataWindow on the DataWindow.

In our case the Surrogate Key would be the display value while the actual key would be the data value; however we are dealing with long lists that do not lend themselves to dddw's. We paint both these columns on the datawindow and then have the nvo copy in the key column value after the user enters the surrogate key. While both columns are modified, only the actual key column is in the list of updateable columns. When 'Key and Modified' is selected, then both columns appear in the where clause, this fails because in our case the surogate key is not in the table we are trying to update. When 'Key and Updateable' is selected then only the actual key column appears in the Where clause.

This leads me to believe that 'Key and Modified' does not look at the Upadatable Columns list when formulating the Where clause. Is this a bug, or is it what PB intended? Newsgroups: sybase.public.powerbuilder.database Date: Mon, 30 Mar 1998 17:14:07 -0500 From: Ron Gallagher Reply-To: rongallagher@mindspring.com Organization: RGI X-Mailer: Mozilla 3.01 (WinNT; I) MIME-Version: 1.0 Subject: Re: Datawindow Update Key & Updateable vs Key & Modified Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 70 Message-ID: References: Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com Xref: forums-1-dub sybase.public.powerbuilder.database:17588 Article PK: 314788. Sean - I just did a little test to verify what I'm about to tell you. The test used a table with three columns (cola, colb, colc). The primary key is cola.

In the first test, the all three columns were included in the 'updateable columns' list and the where clause was set to key and updateable. Every update that was generated included all three columns in the where clauses. In the second test, I left the 'updateable columns' list 'as-is' and changed the where clause to key and modified.

Slimware Driver Update Key

In this test, the where clause in every update included just key and those columns that were updated. I tried this with changes to just one and also both columns, and the results were the same. In the third test, I removed colc from the 'updateable columns' list. When I ran the app, regardless of the changes I made to col c or how I set the where clause, colc was never included in a where clause. Bottom line - If a column is not included in the 'updateable columns' list, then it will never appear in the where clause that's generated by a dw. If the 'where clause' in the update settings for a dw is set to Key and Updateable, then the where clause will include the key columns and every column that is included in the 'updateable columns' list.

If the 'where clause' in the update settings for a dw is set to Key and Modified, then the where clause will the key columns and those columns that the user changed which are also in the 'updateable columns' list. I suspect that you have something else going on in your dw. Ron Gallagher, CPDP Atlanta, GA, USA rongallagher@mindspring.com Sean A.

Update Key West Hurricane Recovery Images

O'Keefe wrote: Let me try and clarify our situation a little more. I believe that PB's standard way of doing what we are trying to do is to place a Drop Down DataWindow on the DataWindow. In our case the Surrogate Key would be the display value while the actual key would be the data value; however we are dealing with long lists that do not lend themselves to dddw's. Camera program for asus laptops.

We paint both these columns on the datawindow and then have the nvo copy in the key column value after the user enters the surrogate key. While both columns are modified, only the actual key column is in the list of updateable columns. When 'Key and Modified' is selected, then both columns appear in the where clause, this fails because in our case the surogate key is not in the table we are trying to update. When 'Key and Updateable' is selected then only the actual key column appears in the Where clause.

This leads me to believe that 'Key and Modified' does not look at the Upadatable Columns list when formulating the Where clause. Is this a bug, or is it what PB intended?