Hi Ray, Just before I read your email I had shut OOo down and happened to have tried to re-open the Intentory odb file. Same problem.
[ In the voice of Dan Akyroid - ala Ghost Busters ] What we have here is a full blown level 3 software anomoly foks, one that remains hidden when it first occurs and then manifests itself later upon database engine re-start! [ my voice now ] At least that is how it looks. To fix this you must open your odb file in a archiving tool. I use he latest copy of 7zip for WinXP. Using this I see that the file is actually a hierarchy of files. You want the file database/script. Edit this and remove the line(s) for the create view using the :Params. Save the file back into the zip file and it will open now. One thing that I have learned over the past 18 months is that HSQLDB and Base can be real 'snickity' when it to comes to making views - 'willy - nilly'. Drew On 9/18/06, Jahn, Ray (R.) <[EMAIL PROTECTED]> wrote:
Frank Schoenheit wrote: > ... JDBC connection test guidance ... Frank, thanks for the instruction. I have completed the tests per your instruction. I am confused by the test results below. I do not have FAX or Agenda on this PC. Not sure what other applications are built on Java (PC config. controlled by employer). Ray ----- OO Java JVM reference: 1.4.2-07 new *.odb: cannot switch to table section JDBC connection: OK, can see tables and views (but ...) JDBC connection test: failed, error dialog below Views V1 and V2 are visible and are displayed empty in OO Base GUI. OO Java JVM reference: 1.5.0-08 new *.odb: can switch to table section JDBC connection: failed, error dialog below JDBC connection test: failed, error dialog below JDBC connection test is the test button during the user account dialog for JDBC connection. ----- OpenOffice.org Base error dialog: Error connecting to the data source Error in script file line: 4 unexpected token: : in statement [(SELECT * FROM TEST1 WHERE VAL LIKE] ----- *** content of the JDBC HSQL *.script file *** *** notice the retention of all Views and the parameter *** It is actually the same test file as originally suggested by Andrew Jensen for the discussion thread of "2.0.3 SQL View and Query parser". CREATE SCHEMA PUBLIC AUTHORIZATION DBA CREATE MEMORY TABLE TEST1(ID INTEGER GENERATED BY DEFAULT AS IDENTITY(START WITH 0) NOT NULL PRIMARY KEY,VAL VARCHAR(50)) ALTER TABLE TEST1 ALTER COLUMN ID RESTART WITH 6 CREATE VIEW V1 (ID,VAL) AS ( SELECT * FROM TEST1 WHERE VAL LIKE :PART_NAME ) CREATE VIEW V2 (ID,VAL) AS ( SELECT * FROM TEST1 WHERE VAL LIKE :PART_NAME ) CREATE VIEW V3 (ID,VAL) AS SELECT * FROM TEST1 WHERE VAL LIKE 'H%' CREATE USER SA PASSWORD "" GRANT DBA TO SA SET WRITE_DELAY 20 SET SCHEMA PUBLIC INSERT INTO TEST1 VALUES(0,'Tom') INSERT INTO TEST1 VALUES(1,'Dick') INSERT INTO TEST1 VALUES(2,'Harry') INSERT INTO TEST1 VALUES(3,'Thelma') INSERT INTO TEST1 VALUES(4,'Donna') INSERT INTO TEST1 VALUES(5,'Harriet') --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
