Quote Originally Posted by Get Em Fast View Post
In post #21 nickgreaves posted "Database Patch Level: 1.3.9a".
Could that have anything to do with his problem, as his database isn't 1.3.9g, while he's trying to upgrade from 'g' to 'h'?
I mean, if he had a "working 1.3.9g", shouldn't the database reflect that?
Just a question..................
Quote Originally Posted by nickgreaves View Post
I don't think there have been any changes to the database structure since 1.3.9a. Certainly it was working fine with 1.3.9g so unless there has been a change between g and h (which isn't mentioned in the release notes), I doubt if this is the issue.

Regards

Nick
Quote Originally Posted by Get Em Fast View Post
Yea, I know the docs say that there has been no database changes since "a", but I was thinking maybe something in the files just disagreed with "a". But, I know you're right.......I'm thinking that too, but I've seen stranger things happen, ya know?

Like I say though, it was just a question.......I already knew the answer before I posted, but curiosity made me post it anyway........haha.....that killed the cat, didn't it?
There is no change to the database revision level between 1.3.9 releases. As far as database revision goes, the letter simply indicates which version was used when first upgrading to 1.3.9xx.

As such, as suggested, it's *not* a related factor.