Customization and Integration

[oyama]

 We had some work done in our database (MAS500 7.3 2011 March update) by a third party and since about that time we cannot print/preview pick tickets. With a little research it turned out that the stock MAS500 report (sozrd003.rpt) prints just fine. However, if I add any table to the report then nothing prints. For example, if I link the timItem table with tsoPickListHdrWrk with ItemKey and add any field from timItem to the report, then the pick list does not print. If I remove that added field from the report then it prints again.

 We already contacted with the third party but they cannot find anything. I can restore an older database and then our highly customized pick ticket prints just fine. I tried with three different servers and the old database prints the new does not print.

We have other forms with extra added tables that prints fine. Only the pick ticket is broken.

Do you guys have any idea/clue/guess what to look for? What could have caused this issue?

[LouDavis]

When you are adding timItem to the report, are you also resetting the database location as well?  I've seen this causing issues when this isn't done.

[oyama]

What do you mean by " resetting the database location?"

[JohnHanrahan]

If you look at Set Database Location (under database menu option) and don't find anything wrong I would do a detailed trace with errors and warnings.  Maybe something will pop up there.  It kind of smells like a security problem.

J

[oyama]

Ok, got it. I went through all the tables and replaced all of them with "Create New Connection\ODBC\MAS 500\mas500_app\dbo\Tables\". So, all the table source is coming from one server and one database. Unfortunatelly, it did not help.

What kind of security could cause this?

I just would like to add that nobody can print modified pickticket. And everybody can print the stock pick ticket.

[trodman]

If you can restore the older database and successfully print the pick ticket, I would assume that the problem is unrelated to the Crystal report itself.

1. Is the "Set Up Business Forms" entry the same in both databases?
2. Is the structure of the tsoPickListHdrWrk the same in both databases?
3. Is the spsoPrintPickList procedure the same in both databases? You could check the modified date in sys.procedures.
4. Are you using the same client environment when connecting to both databases? If not, does the crystal report exist in both client environments?

[LouDavis]

Have you run a detailed SQL trace to see if an error is occurring on the backend that simply isn't being displayed to the user?

[oyama]

Well, finaly figured out what caused the pick ticket to break. We purchased WA module and when we activate/register the WA module the pick ticket stops working. It is quite odd,  since the two things should not be related. Now, we just have to figure out who is going to fix this issue. Sage or Scanco...