new comp, new intstall. Company opens, but when posting a payable to a job "unable to find data dictionary alert functions @j81aart,(1212)" comes up. It appears to post after that. It shows up in the general ledger, but no trace makes it over to jobcost...

Hi RJCC,

An 'error 1212' always refers to a problem with the installed data dictionaries, and typically is caused by the correct ones not being there. The error message you posted listed the @J81A dictionary, or the Adagio JobCost 8.1A dictionary, which works for version 8.1A and 8.1B, but not the current version of JobCost 8.1C - which has a different and updated dictionary file @J81C. The likely problem is that the correct dictionaries were not installed.

What versions of Adagio Payables and Adagio JobCost are installed? You can check this from the Help menu and About within each program. If you have the current version of JobCost 8.1C, you should reinstall that program, and ensure no-one else is using Adagio.

Jobs can be modified to include Alerts, and you can specify which functions pop the alert, such as invoice entry from Adagio Payables, when the job is selected. Alerts will be ignored during the posting of a batch.

After posting in Payables, you need to Retrieve the batch into JobCost, from the Maintenance menu and Retrieve batches. If the retrieval file was correctly written to by Adagio Payables, then the checkbox for Payables will be selected here. This batch retrieval screen can automatically appear when you start JobCost by settings in User Preferences for what to auto-start on sign-on.

Following this up. @j81aart does not exist in \softrak\dict.

However, it does not exist in my \dict folder either, or, apparently, in the one in use by Softrak tech support. Yet no problems are being encountered in either of these locations.

So the question becomes: "Why is AP seeking a non-required dictionary file?"

Hi Ralph,

@J81a??? would be a table within the @J81AI.ssi / @J81AR.ssi dictionary pair.

Can you confirm what version of Adagio JobCost is installed? In the \softrak\dict directory, can you see @J81A and/or @J81C? With thier data in your office, can you replicate the problem? This can help determine if the issue is related to their installation, their data, or the program.

To close this thread, at Leigh's suggestion, I copied the @J*&.ssi files from my system and the problem resolved itself.

Hello Ralph:
Your response is a bit unclear. Is this what you mean?

You copied all the files @j*.ssi from your computer to the client's system that was having the issues. (Not sure what the
"&" character is all about in the filename.)

Just want to verify your solution.

Be aware that copying dictionaries from one system to another is not advisable unless there is clear evidence that the dictionaries on the "problem" machine are corrupt or were not properly updated.

You should determine what has caused the problem with the dictionaries.

BTW, using a set of "mismatched" dictionaries may cause DIC errors in the associated application!

Michael: So is Ralph just "lucky" that he seems to have fixed his issue?

No, Michael is taking the official position. The unofficial position is that what Ralph did usually works, and if you make a backup of the DICT folder first, it is worth a try.

Steve

All good with Ralph except an explanation of why the dictionaries were incorrect.

What I am saying is that copying a set of dictionaries that are not "correct" for the underlining application, and which may not be noticed by the application, can cause problems.