Hi Jeff:
The solution is to use a combination of parameters in the profile
definition of the Oracle conection (in PB). Make sure that case is not
considered by deactivating Case Sensitive (which is the default value
and it's the same to add "MixedCase=0" to DBParm) and that the syntax
tab indicates not to delimit column and table names with double quotes,
deactivating "Enclose Table and Column Names in Quotes" (the same as
DelimitIdentifier='No' in DBParm). This tells PowerBuilder not to add
double quotes to SQL commands, so that column and table names may be
translated into uppercase and it also allows you to view and edit all
Datawindows created with lowercase (specially those in PFC).
A better explanation and references follow...
William Ulate
Analista/Programador
Sistema de Informaci�n sobre Biodiversidad Atta.
Instituto Nacional de Biodiversidad.
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
This is what we know so far:
This error is related to ORACLE. It is caused because some DataWindows
have been created in other database engine (SQLAnywhere or Sybase,
probably) and now it is run against ORACLE. This error appears in the
PFC DataWindows and in utilities (like the Security Adm) that comes with
PFC.
If you set "Case Sensitive" in the connection profile then the already
created DataWindows will give an error because they were created in
lowercase and they are not translated into uppercase when consulting the
database.
ORACLE's dictionary is all in uppercase (and that is the way ORACLE
works internally and the way it expects the names to be!): the table and
column names will not be found if the SQL command sent to the database
has some of these in lowercase or if you use mixed case. This is why
ORACLE converts all queries it receives (table and column names) to
uppercase, EXCEPT when double quotes are used to delimit those names.
PowerBuilder is case sensitive (as I guess other engines must be) and
when it generates the Datawindow's SQL command, it considers the way the
database sent those names.
Besides, ORACLE states clearly that double quotes should not be used for
the column and table names because if they are used, then the case is
relevant and this can be a nightmare for users and developers. To use
alternative solutions like creating aliases for table and column names
is not adviced (sp?) (look at the reference). Neither it is to change
everything to uppercase (with SQLC[ase] parameter) because this also
converts the data.
References: Sybase Infobase Issue #437571. The customer is developing
his application in SQLAnywhere and wants to run it against Oracle too.
Book: Oracle8. George Koch & Kevin Loney. The Complete Reference. Oracle
Press. Pgs. 42, 265 y 425.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 27, 2000 5:07 AM
To: [EMAIL PROTECTED]
Subject: PFCSIG Using the PFC Scanner using Oracle 8.0.4
Hi everybody,
I have a problem using the Scanner application of PFC when I'm
connected
to Oracle. When I try to click the scan button to scan a window,menu or
a
datawindow on a certain PBL, an error message pops up that says
"Database Error
Code: 904 Select Error ORA-00904: Invalid Column Name". I only
encounter this
error when I'm connected to Oracle, however when I'm connected with
Sybase or
ODBC , I do not encounter this error. Can somebody out there who had
encountered this problem before help me. I would be very grateful.
Tan Agustin
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
"The information in this e.mail and any attachments is confidential and
is
intended for the addressee only. Reading, copying, disclosure or use by
anybody
else is not authorised. The contents do not represent the opinion of SGS
Soci�t�
G�n�rale de Surveillance Holding SA or any of its affiliates except to
the
extent that it relates to their official business. If you are not the
intended
recipient, please delete this message and any attachments and advise the
sender
by return e.mail"
Visit our website: http://www.sgsgroup.com
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE
COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help
pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
