Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Need To Dummy-Down Oracle

Re: Need To Dummy-Down Oracle

From: Van Messner <vmessner_at_netaxis.com>
Date: Sat, 5 Dec 1998 19:31:04 -0500
Message-ID: <Fika2.1350$f91.5270@news14.ispnews.com>


Both the two prior answers are right. Make sure you've set the proper columns as updateable and if you place your own SQL into the datawindow SQL painter you will have to qualify your columns with the table names (and use double quotes and a bunch of other dumb PB stuff).

Michael Smith wrote in message <3669CA12.F5DD27AC_at_teleport.com>...
>There is no need to disable the referential integrity restraints on the
database
>- the problem is in your datawindow. Check the "Update Properties ..."
menu
>item for the "Rows" menu in your datawindow object and you will probably
find
>that the columns you want to update are not specified as allowing updates.
>
>This is one of the most common datawindow problems. When you change a
>datawindow after it was originally created, PowerBuilder often requires
that you
>manually specify the new column update properties (I suspect that this is
for
>safety purposes).
>
>HTH,
>Michael Smith
>Certified PowerBuilder Developer
>
>Doug Stone wrote:
>
>> Hi. I have to implement, in Oracle, a db that includes duplicate column
>> names.
>>
>> For instance, emp_id is in the employee table, and in the address table.
>>
>> The application was build with PowerBuilder datawindows.
>>
>> If I setup correct RI between all the duplicate column names, the
>> datawindows will fail.
>>
>> Does anyone know how I can, temporarily, disable Oracle insistence on
unique
>> column names?
>>
>> Thank you,
>> Doug
>
>
>
Received on Sat Dec 05 1998 - 18:31:04 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US