-
1
- #1
With ES 9.5 it is impossible to run an AR Aging Analysis report, it's a known bug that will bring everything to a halt. Users will get timeout and their screens will freeze. You then, as the IT guy get the blame for it all. Since Macola probably won't fix this for months, I had to come up with my own solution, so here it is:
I have a .vbs script that is run at 7am every morning, which builds a table called 'AgeT'. This table has all the aging analysis data you need. It takes about 30 seconds to run.
I will post the .vbs code, and the code to run it.
Attached is the .vbs file (rename it from .txt to .vbs) alter the first lines of the file to point to your server/database.
Go into enterprise manager and create two jobs. The first is to Create the job to run the .vbs file. Point the database to 'master' and in the Command section, type the following:
exec master.dbo.xp_cmdshell 'cscript c:\vbs\age.vbs'
Of course change the location of where the file is, if you save it elsewhere
The next job is to create another job to DROP the table, since it won't create a table if it already exists.
The code for this is:
DROP TABLE AgeT
Schedule the DROP job to happen a few minutes before the Create job is to happen.
Once it creates the table, use an access database or ASP to reference the table.
The fields that you really need are:
Cus_No, Cus_Name, T1, T2, T3, T4 (which are < 30 days, 30-60 days, 60-90 days, > 90 Days)
Hope this helps you, this was the only workaround I found. It does work and it is accurate (I verified it with the reports that Macola generated)
Test on a test databse first, let me know if you have any problems.
I have a .vbs script that is run at 7am every morning, which builds a table called 'AgeT'. This table has all the aging analysis data you need. It takes about 30 seconds to run.
I will post the .vbs code, and the code to run it.
Attached is the .vbs file (rename it from .txt to .vbs) alter the first lines of the file to point to your server/database.
Go into enterprise manager and create two jobs. The first is to Create the job to run the .vbs file. Point the database to 'master' and in the Command section, type the following:
exec master.dbo.xp_cmdshell 'cscript c:\vbs\age.vbs'
Of course change the location of where the file is, if you save it elsewhere
The next job is to create another job to DROP the table, since it won't create a table if it already exists.
The code for this is:
DROP TABLE AgeT
Schedule the DROP job to happen a few minutes before the Create job is to happen.
Once it creates the table, use an access database or ASP to reference the table.
The fields that you really need are:
Cus_No, Cus_Name, T1, T2, T3, T4 (which are < 30 days, 30-60 days, 60-90 days, > 90 Days)
Hope this helps you, this was the only workaround I found. It does work and it is accurate (I verified it with the reports that Macola generated)
Test on a test databse first, let me know if you have any problems.