Hi Paul

Another day, another new query I NEVER EVER have dealt with before

Which makes my job so interesting!

Let's start with the very basics:

1. If not yet done so, close the company and delete the relevant agent's Registry Editor Key on the local PC.

Open the company and check if still a problem. 

2. I this a segmented GL accounting company? 

Kind regards

Bennie 

Hi Paul

Another day, another new query I NEVER EVER have dealt with before

Which makes my job so interesting!

Let's start with the very basics:

1. If not yet done so, close the company and delete the relevant agent's Registry Editor Key on the local PC.

Open the company and check if still a problem. 

2. I this a segmented GL accounting company? 

Kind regards

Bennie 

Hi Bennie

Thank you for your feedback.

1. I was working on the server with the Admin password as opposed to the agents pc and password, so I am not expecting this to be a factor.
2. Standard ledger.

Kind regards
Paul

Thanks Paul

Please do the following:

1. See if you can perhaps find that specific transaction on the POSTGL table.

Your SQL query should of course include the relevant WHERE BY clause filters to find what you're looking for. 
Do you think you'll be able to manage that?

2. Because of you do. you now need to compare this specific transaction in the POSTG: table in a field value by field value comparison with other records that ARE included on the GL Account Transactions report.

You may find that perhaps one or more fields have a NULL or blank value where the other records don't, or vide versa.

HI Bennie

You nailed it! - turns out that the Period column in POSTGL reflected 0.
Would have expected a GL relink to pick up that the period was incorrect though.

Thanks for you assistance Bennie.

Take care
Paul

NICE!!!!!!!!! 

ALWAYS A PLEASURE, PAUL!!!

Glad I could help!

Thanks - this worked for me as well.

Fantastic!!!