p51b.mustang wrote:

> 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?

Backing up in the old version and restoring in the new is fine moving forward.
The think to make totally sure off is that you test the new set-up fully before
committing to production. While a couple of my sites have moved to FB2.5 without
a problem, the third upgrade started locking up every couple of days, and so I
had to drop back fast. But I am still using some legacy windows based code as
well, which may be the problem there. The PHP side of things does seem to be
fine. My hassle was moving a couple of weeks of data from the 2.5 database BACK
to the 2.1 version, but fortunately Flamerobin does a good job with 'save as
insert' ;)

--
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