RE: PO Report Customization Package stops working
Hi
Definitely sounds like two different reports dictionaries.
A few things to note that may help you with this one. To find the location of forms and reports dictionaries, open the Dynamics.set file that is used to launch the application. It shows the list of products installed. At the bottom of the list is the pathname for all the dictionaries. There are three lines for each installed product. First line points to the main dictionary and should always be pointed to the C drive location where the program is run from. The next two lines point to the Reports and Forms dictionaries.
In multi-user environments you have two options for where the Forms and Reports are stored. (Just as an aside - the Forms or Reports dictionary only exists if there are customised items). You can store them locally - C drive location where the program is run from - or in a shared location.
Most sites prefer a shared location because you then don't run into a situation where you have "dictionaries out of sync". And when you get a site (like I currently have) where everything has been kept locally and there are lots of modifications, you then get to a point where you have no idea which is correct.
A shared location can cause minor issues with things like importing packages, however, there are ways and means to get reports in while users are logged in, so it is a minor issue.
If you choose to use a local dictionary, you can put things in place to ensure all dictionaries get updated. The site I worked at as a user had all local dictionaries. It meant we could make changes without impacting others. BUT - we had a global master and there was some form of script (don't ask me the details on that one) that at log in compared the master with the local copy - if they were different, the master was copied down. So if we made changes that we wanted to keep, we overwrote the master to make that the new one. Everyone got the new report by the next day at the latest.
Hope that helps.
Cheers
Heather