That looks familiar...
Look at the next line in the sql script. I had dbimport crashing like
that because there was a non-ascii character in a comment inside
a stored procedure.
Cheers,
Dirk
--
-- Dirk Gunsthoevel IT Systemanalyse phone: +49 (0)251 624947
-- Steinfurter Str. 61 fax: +49 (0)251 1624111
-- D-48149 Muenster http://www.GunCon.de/
-- "The cost of living hasn't affected its popularity."
"Alejandro" <alejandro@siu.edu.ar> schrieb im Newsbeitrag news:cb3b6cd4.0312041226.2178d935@posting.google.com...
> Guys, I could create a new DATABASE with dbaccess or SQLEditor.
> I had no problem.
>
> I checked the dbimport.out file, but it doesn't give me a message
> error , just only like follow:
>
> ...
> ...
> ...
> create procedure sp1 (....)
> begin
> define error_number integer; -- Error Number
> define error_msg varchar(255); -- Error Message>
>
>
> Only this.. No more!
> DBIMPORT break and it didn't send any message.
> If I edited the SQL archive of dbimport and take out this procedure,
> when I repeated the dbimport, the error is caused in another create
> procedure...
> with no message error, of course!!!
>
> I don't know what to do. I had no problem importing this "export" on
> Infomrix Dynamic Server on Windows NT Server 4.0.
>
> TIA