If your backup from 2/2 allows posting, you check the account_checkpoint
table for differences, and also the defaults table.
Did you do any upgrades or close books?
On Thu, Feb 25, 2016 at 11:31 PM, Hilton Day wrote:
> I checked my backups - and my previous copy of the database dated 2/2
> allo
I checked my backups - and my previous copy of the database dated 2/2
allows posting, so having done a diff of the SQL files using pg_dump, I'm
just going to revert and post the various transactions again since then.
Still not clear what I did to cause book closure, but at least a way
forwards tha
Hi Chris, thanks.
Do you have a save button?
>
>
Yes, but it doesn't proceed the workflow to enable "Post as Saved" as I'm
used to seeing.
Hitting Save results in a request to the web server, and it populates the
Due Date field, but no Post buttons appear.
>
> If that s missing then the proble
On Sat, Feb 20, 2016 at 10:21 AM, Hilton Day wrote:
> Many thanks Erik for the speedy response.
>
> Upgrade completed to 1.4, and then subsequently to 1.4.24, and I can open
> the accounts, so upgrade is considered successful.
>
> However, here's a question for the brains-trust of ledgersmb exper
Many thanks Erik for the speedy response.
Upgrade completed to 1.4, and then subsequently to 1.4.24, and I can open
the accounts, so upgrade is considered successful.
However, here's a question for the brains-trust of ledgersmb experts on
this list :)
I still can't post an AR invoice - I don't g
Hi Hilton,
On Thu, Feb 18, 2016 at 8:33 PM, Hilton Day wrote:
> I'm trying to upgrade my old 1.3.46 database (started life as 1.1 from
> memory - back at end of 2006), and have worked my way through a few issues
> so far, like a few duplicate meta numbers, and missing GIFI accounts.
>
Ok. Then
