Armaghan,
Will keep that in mind. With helpful hints from everyone here I figured
out the issue and corrected it. Apparently ,after I had run quarterly
closes, I did not lock the books, so someone (I will assume me) moved a
couple transactions from one period to another. I found those
transactions, fixed them and locked the books down.
I'll save this information, if I ever need to use LedgerDoctor.
Thanks,
Jeff
On 10/18/2011 17:31, Armaghan Saqib wrote:
On Tue, Oct 18, 2011 at 9:12 PM, Jeff Kaminsky<[email protected]> wrote:
3. Armaghan,
We are using SQL-Ldgr 2.8.23, is LedgerDoctor or something simliar available
for a non Ledger123 accounting system?
Hi Jeff,
Yes, you can use LedgerDoctor on non-ledger123 systems. Here is what
you need to do:
1. Pull custom_am.pl, and mylib.pl from github. (If don't know how to
do it, I shall send you directly)
2. Add following to your menu.ini at appropriate place:
[System--Ledger Doctor]
module=am.pl
action=ask_dbcheck
If you discover some issue which LedgerDoctor does not catch yet, I
shall be happy to add detection/rectification code for it in
LedgerDoctor.
Regards
Armaghan
_______________________________________________
SQL-Ledger mailing list
[email protected]
http://lists.ledger123.com/mailman/listinfo/sql-ledger
--
Jeff Kaminsky
Sr. Accountant / Logistics
IX Systems
408-943-4100 ext 122
408-943-4101 fax
_______________________________________________
SQL-Ledger mailing list
[email protected]
http://lists.ledger123.com/mailman/listinfo/sql-ledger
