I tried on WinXP with OOo 3.0.1.

You use complex Primary key, and try to insert same PK twice:
last row in your Script cause problem:
INSERT INTO PUBLICATIONPHRASE VALUES('AMWE', 'ES', 'tocmain',....
gave error:
1: Violation of unique constraint SYS_PK_77: duplicate value(s) for column(s)
"PUBLICATIONID","LANGUAGEID","PHRASEKEY"

But if I try to re run SQL command crash. But if I waited one minutes and tried
to run command, only error msg came up and no crash.

If I deleted all records from Table and re-run all script, and clicked on Table
name crash, and after file recovery table empty.

If I re-run script without last row (no duplicate PK), click to table crash.
If I click on other parts of Base(Queries, forms,reports no crash), and after
that click back to table, the table opens very slowly, PHRASE field is memo
filled with lot of texts.

I tried it in DEV310m1, same crashes. 

I think all connected to PHRASE, memo type field, when insert long text into it
cause crash. 

confirming, targeting, assigning

fs->oj: Just open the database from the ZIP document, do to Tools/SQL, and
enter/execute the *last* statement from the SQL script. This will crash OOo.

If you run this in a debugger, then there will be multiple assertions from the
runtime library, saying something about bad allocs, coming from our parser
implementation.

fs->demcadams: Do you mind to attach the database and the SQL script here at the
issue (see the "Create new attachment" link above)? This would ensure that the
documents are available as long as the issue lives, which might not be
guaranteed for the ZIP file you linked. It would be sad if the issue cannot be
reproduced and fixed later because for whatever reason, the ZIP has gone. Thanks.

Fixed in cws dba32b

Please verify. Thanks.

looks good in CWS dba32b