Hi
I have been trialing billings v2 (2.05b206) and have built up a small database.
Now downloading the new v2.5 - when i click it to launch i see a couple of quickfire 'updating database' boxes and then it immediately crashes. If i try to alunch it again it crashes spontaneously, without any activity
I have tried the ususal
- reinstalling
- restarting
- repairing permissions
- trashing preferences
- even trashing the cache folder

and
moving out the existing library > application support > billings folder and starting with a fresh v2 databse, adding one project and one working slip
... the same thing happens

the only way that i have got v2.5 to launch is to move out the whole existing library > application support > billings folder and start with a fresh v2.5 database

anybody else experiencing this??

powerbook G4 1.67
2GB ram
mac os x 10.4.9

I have exactly the same issue.

I launched my trial copy of 2.05 today having used it for a week or so and then it prompted me to download the 2.5 upgrade. It didn't finish the installation successfully and then would crash at every relaunch.
After deleting the library files and installing 2.5 cleanly from a new download it loaded, but once I quit the app and tried to relaunch...same problem. Crash crash crash. What's going on guys?

I had a few templates and a few bits of client data/invoices I would like to retrieve (and continue using!). I really liked the application before the crashing incident and so today I purchased a license (still awaiting the serial number) in the hope that once I get that it should stop the problems... fingers crossed.

FYI I am using 10.4.9, 1.33GHz 768mb ram

We are looking into this.

Actually I do have a thought (surprise). When you launch Billings and it crashes - do you see an error in the console?

You can launch the console app by going to HD -> Applications -> Utilities

I think it is a corrupted file on disk that the app is reading.

Please refer to the following knowledgebase article to resolve this issue.

http://www.billings2.com/support/article.php?id=051