The big problem in this case was starting with a v2.0.8 backup file & a fresh v2.8.31 database schema. As you can well imagine, quite a few changes that had to be made. SL is very flexible -- it can start with an existing v2.0.8 database & migrate it to the latest version, but it cannot be expected to sniff an old backup file & make it fit the new schema.
What I ended up doing was dropping all the tables/sequences, & restarting. I let SL recreate everything, then I went in there & read each error message while loading the data from my backup file, attempting to correct as I went. That worked much better, & I think I have something that will fly now. We'll see! -- Best Regards, Wallace _______________________________________________ SQL-Ledger mailing list [email protected] http://lists.ledger123.com/mailman/listinfo/sql-ledger
