Administration, Core Financials, and Project Accounting

[Midknight_Tranz]

Hi Guys,

I have been able to successfully setup FRx 6.7 and was able to create my Rows, Columns and Catalogs.

Unfortunately, when I generate the report this error appears:

"01000: [Microsoft][ODBC SQL Server Driver][SQL Server] The statement has been terminated"

Has anyone of you experienced this?

Best Regards,

[Midknight_Tranz]

Has anyone encountered this?

[Jima]

Did you retry to build the GLX indexes? Go to the admin menu and select 'Build Local GL Index'. Or you can close FRx (on all clients if you share the sysdata folder on multiple clients), rename the .glx/g32 files in the sysdata folder - don't delete in case you need those files. Just rename the file extension to something like '.bad' or whatever. Then run FRx again and it should tell you it is rebuilding the GL index.

[Midknight_Tranz]

Hi Guys,

After alot of tests, I have been able to isolate this error.  I encounter the abovementioned error when generating reports for specific accounts namely:

410100

410500

410600

410700

410900

411200

411300

411500

411700

411800

411900

412000

412100

412200

These accounts are all SALES accounts.  The wierd thing is this doesn't happen for ALL sales accounts.  You may notice that there are gaps in between the account codes mentioned above.  Has anyone experienced this type of error in FRx when it comes to specific account?

[Midknight_Tranz]

Just an update, I finally found the cause of the error.  Apparently there are account wherein part of the acount code is not maintained in the sement maintenance.

For example we have an account main account of 410000 and segmant 3 as Department (e.g. 0, 1, 2)

Based on the info above we would have 3 possible account codes namely:  410000-0,  410000-1 and 410000-2.  What I found was that there were some additional accounts e.g.  410000-A and  410000-B.  Now when we generate a TB based on the main account only, FRx can't find the departments A and B since it wasn't maintained.  This was the cause of the error.  When I created a tree to exclude the additional departments, the report generated smoothly.

My porblem now is I can't explain how these accounts were created and I'm sure that we had automatic creation of accounts turned of from the start of our implementaion.

Anyway, thanks for listneing guys