Selecting ranges for reports 1

[RemJamie]

We used to be able to pick an account range for a report and now we have to pick a segment range for each segment of each account that we want, this is very time comsuming at month end and is quite annoying. If we do enter a range using the account # the reports print with no records/accounts on them.
Is there a setting somewhere to fix this?
I am on version 8.0
Any help would be greatly appreciated as I am kind of new to Great Plains.

 

[Luvsql]

Which report in particular is the issue, as the Finacial trial balances can still be printed by account.

 

[RemJamie]

Almost all financial trial balances, I believe have this problem. I am not sure what you mean by saying they can still be printed by account? I can not print anything if I pick an account only if I pick the right series of segment values.

 

[Luvsql]

Just curious, could you run check links on the account master? It sounds like your segments are not updated.

Can you select an account range using Smartlist > Account Transactions?

 

[RemJamie]

I ran check links and it does not help.
I can pick a range in smartlists.
I might help to know we ran a changer program to change our account number structure and this is when we started having the problem, I should have mentioned that before sorry, maybe we forgot something after doing the changes to our account numbers?

 

[Luvsql]

One thing to try is to run this in query analzer (if SQL):

DELETE GL00105

THen run check links on the account master again.


If not on sql, you can go to file > maintenance > clear data, choose financial, then click on Display and change to physical instead of logical (very important), insert Account Index Master, okay. Then run check links on the account master.

If that fails, you could also try re-creating your Segment master (GL40200).

The changer doesn't change the index numbers, but changes the account number, then any other field that references the entire account number, instead of just the index.

 

[RemJamie]

Thanks a lot this fixed the problem.