Thanks for the heads-up. I plan to convert the old databases across to the current version; the big mistake was allowing those on top dictate no upgrades for the past 5 or so years (where are they on the weekends?). Wouldn't a restore of a backup do most of the data conversion?
David

--- In firebird-php@yahoogroups.com, Lester Caine <lester@...> wrote:
>
> p51b.mustang wrote:
> > The suggestion by Tom to place the fbclient.dll into the php.exe directory did the job. I guess the load proc in the php_interbase.ini expected the fbclient.dll otherwise ..... Maybe the dll should be called php_firebird.dll:-)
> > Anyway, at least I'm getting somewhere.
> This is one of the areas that creating a specific php_firebird.dll would be nice
> to do ... The other thing to bare in mind is that a newer client SHOULD still be
> able to access an older database. I'm still running 1.5 on some sites but with a
> 2.1 client since they have got a new database being tested as well. But this may
> be something that may be more by luck. The mechanism for backing up new
> databases using an older gbak so you can maintain legacy sites seems to have
> been lost with 2.5 :( Just been stung by that one since 2.5 will not run one of
> my older databases reliably and had to shift back to 2.1 fast.
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk//
> Firebird - http://www.firebirdsql.org/index.php
>