At 02:19 AM 28/04/2009, you wrote:

>Hi Helen thx for the information, i been reading the release note doc, "Metadata Text Conversion" only i had a doubt that error no appear for example any procedure with any "select", "update", "insert", "delete" sintaxys used only in FB 1.5? or the problem is because the metadata had problems to convert?

You originally wrote:
-------------------------
3.- i can see the table and triggers but when i try to access to any procedure bring a error message said

SQL TEXT
select pr.rdb$procedure_name,
pr.rdb$procedure_source,
pp.rdb$parameter_name,
pp.rdb$parameter_type,
fs.rdb$field_name,
fs.rdb$field_type,
fs.rdb$field_length,
fs.rdb$field_scale,
fs.rdb$field_sub_type,

ERROR MESSAGE
Cannot transliterate character between character sets.
Cannot transliterate character between character sets.
-------------------------------

That's the error you get because you did not do the metadata text conversion. Chunks of text in metadata that used to be stored in ANSI are now stored in Unicode.

In case you did not realise it, the restore does not re-compile your pre-processed things (triggers, stored procedures, view BLR, CHECK constraints, etc.) Fb 1.5 used one encoding; Fb 2+ uses a different encoding. Hence, the scripts are provided to enable you to perform this migration without needing to think through a solution yourself.

./hb