Thanks for your reply. Yes, the problem is reproduced on EMS but not with Flamerobin.
I'm not in the same with you. I've not recompiled a stored procedured. I can't determine exactly the problem origin. I've backuped and restored the database but this's did'nt resolve the problem. I gues that the problem is releated to Firebird version. I'm trying to port the database to Firebird 2.5.8 because the problem is'nt reproduced with this version on Mac OS. Bien cordialement. *Mourad **Hedfi* Directeur de projets Tél. : 01 83 62 36 85 2018-06-12 15:24 GMT+01:00 blackfalconsoftw...@outlook.com [firebird-support] <firebird-support@yahoogroups.com>: > > > I am assuming that you are getting such an error with the db-manager you > are using. > > I have seen a similar issue when using my EMS Firebird Database Manager. > > This often happens after I have recompiled a clean stored procedure > several times with new modifications. > > I wonder if these issues are related. > > EMS Technical Support has responded that they hope to have such issues > corrected by the next upgrade release. From their point of view it is a > db-manager issue. > > Steve Naidamast > http://www.blackfalconsoftware.com > > > >
