ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Problem Reports - Repeatable >> Problem Reports
http://www.istechforum.com/YaBB.pl?num=1076093656

Message started by Lynn Pantic on 02/06/04 at 10:54:16

Title: Problem Reports
Post by Lynn Pantic on 02/06/04 at 10:54:16

This Forum Board is intended for specific DBA program problem reports that can be clearly defined and are repeatable. We at IS Tech Support will use this section of the board as programming direction as far as bug fixing is concerned. Generally, if a problem can be clearly defined and is repeatable, it can be fixed fairly easily.

Please always include the specific DBA program you are having the problem with and the version you are on.

If you have previously posted a report on a different board and it has not yet been fixed (as of the 1/30/04 update), please repost to this board.

Title: Re: Problem Reports
Post by JoelW on 02/18/14 at 07:42:42

We recently upgraded DBA classic to EVO and are in a transition period. We are using both DBA classic and EVO, however, when I run the AP aging report (T6APi1.RTM)in EVO, the invoice numbers are referring to a reference number (BKAPINVT.BKAP_INVT_NUM) rather than the actual Invoice number. But when I run the AP aging report in DBA classic, it has the correct invoice numbers.

Is there something wrong with the AP Aging report in EVO?

Title: Re: Problem Reports
Post by Lynn_Pantic on 02/18/14 at 07:51:33

You need to copy the AP Aging and check RTMs from the RTX subfolder to the main folder and renaming them from RTX extension to RTM, replacing the old RTMs.

Title: Re: Problem Reports
Post by JoelW on 02/19/14 at 05:58:40

The AP aging report worked like a charm. However, I also knew the file name I was looking for. What file names are for the checks?

Title: Re: Problem Reports
Post by Lynn_Pantic on 09/29/14 at 08:38:12

Copy all the T6APH*.RTX to RTM and you will get all of theem.

Title: Re: Problem Reports
Post by Mark Daley on 11/20/14 at 09:46:36

The Labor/Production Exception Report (which comes up after the DC-H module in DBA Classic) gives an I/O Error 103 when trying to print. This is the only report that does this that I've come across in our installation.

Title: Re: Problem Reports
Post by Lynn_Pantic on 11/20/14 at 12:33:07

Look in DBAMFG for files named TAS3746.TMP where the 3746 is a random hex number. If there are any there, delete them. If there are a lot of them, you need to look at the user permissions to the DBAMFG folder.

Title: Re: Problem Reports
Post by Mark Daley on 11/21/14 at 08:57:24

I deleted the .tmp files, checked permissions on the folder (no restrictions), and even restarted my DBA client. Same error. Not a deal breaker, really, just wondering if there was a fix for it.

Title: Re: Problem Reports
Post by Lynn_Pantic on 11/21/14 at 11:06:35

Update from your 10 year old version.