To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=49750
                  Issue #:|49750
                  Summary:|OOo Base rewrites SQL queries created in SQL View
                          |incorrectly
                Component:|Database access
                  Version:|OOo 2.0 Beta
                 Platform:|All
                      URL:|
               OS/Version:|All
                   Status:|UNCONFIRMED
        Status whiteboard:|
                 Keywords:|
               Resolution:|
               Issue type:|DEFECT
                 Priority:|P2
             Subcomponent:|none
              Assigned to:|msc
              Reported by:|dwithers





------- Additional comments from [EMAIL PROTECTED] Mon May 23 14:11:16 -0700 
2005 -------
Background:
I am trying to use OpenOffice.org Base to query a Progress database via ODBC.
The database is holding information for a business system called Syteline
(version unknown), and has many table and column names that are not SQL
compliant (they contain dashes).

Issue:
The SQL89 specification Progress uses allows access (but not creation) of these
tables and columns, but Base will not allow me to query them. When I create the
statement in Design view, fields like cust-num become cust - num. What's more of
a problem is that even if I write the query directly into SQL view, it is
rewritten in the same fashion before it is saved or executed.

How to reproduce:
- Create a new Base file connected to a "MERANT 3.70 32-BIT PROGRESS" ODBC data
source.
- Select "Create Query in SQL View"
- Enter a query such as "SELECT cust-num FROM artran"
- Save the query with any name
- Close the query, then right-click on it and select Edit
- Attempts to switch off Design View are met with the error "The table "artran"
is unknown in the database."
- Attempts to run the query are met with the error "Table XXXX does not exist or
cannot be accessed." (where XXXX is the name of the database which was 
connected to)
- A packet capture reports that the query which is actually sent is now "SELECT
 cust -  num  FROM   XXXX . artran  artran  WHERE  0 = 1  FOR READ ONLY" (where
XXXX is the name of the database which was connected to, and take note of all
the spaces which have been added... the reason the statement now returns an 
error)

Alternate method:
- Create a new Base file connected to a "MERANT 3.70 32-BIT PROGRESS" ODBC data
source.
- Select "Create Query in SQL View"
- Enter a query such as "SELECT cust-num FROM artran"
- Attempts to run the query are met with the error "Column cust not found in
table artran"
- A packet capture reveals that the actual SQL string sent is "SELECT  cust - 
num  FROM  artran  WHERE  0 = 1  FOR READ ONLY" (once again, several spaces have
been inserted which completely change the meaning of the request)

Environment:
OS: Windows 2000 SP3 on an Intel x86 (Dell Optiplex GX150)
Database: Progress 9, exact version unknown
ODBC Driver: MERANT 3.70 32-BIT PROGRESS
OpenOffice.org: 1.9.104

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to