I have some customized sales order reports that were printing the text associated with the customer master using tccom010.txta. Since an upgrade to porting set 6.1c.06.01 and installation of patches related to solution 150185, and replacement of some standard program objects (like ostpstandard, ostp_stddll, ostp_textdll) the text that prints is not the text associated with the customer record. We get text that looks like help text and sometimes it looks like code from scripts.

Can anyone offer advice?

Just a guess - since I am not real familiar with porting sets, patches and such. Any way do the text numbers in tccom010.txta and the text in tttxt010 match? By that I mean when you look up the text number in the text table does it have the correct text? I am just wondering if for some reason some indexes are corrupt. We had a case when you ran the Baan program and did a lookup using the index it returned a different record than what table maintenance returned. We rebuilt the indexes and everything was fine.

Just my humble guess. Good luck!!

Mark

Tried that a while ago. The value in tccom010.txta retrieves the right text in tttxt010.

Thanks for the suggestion.

Hi there,

as you mentioned that the incorrect texts seem like help texts or suchlike, just try and look up the text number in company 000.
If you find the text that is printed on your reports here, at least you are step further. Anyway you should find a patch on the Baan pages, if the company number gets messed up.

Another shot in the dark, too, that is.

regards

Norbert

This may not be your problem, but this is a problem I saw with a customer not too long ago. This corporation had multiple companies with some logical/physical relationships. In this particular case, tables tdpur040, 41, and 45 in company 600 were logical with physical counterparts in company 500. They were printing the footer text from tdpur040 and the line text from tdpur041. Everything was going along fine until they installed IVc4 SP8. Then the texts started coming up wrong. It turned out that even though you could see the correct text number coming up in the report debugger, it was taking the text from the physical company with the same text number (i.e., instead of grabbing text #10000 from company 600, it was taking it from 500). The really interesting piece was that this only happened IF the report field was a table field. So, if I put tdpur041.txta on the report, it had a problem, but if I assigned the same text number to txtn.ptr in the program script, it printed fine in the report.

It was fun trying to diagnose that one!:) Again, it may not be your issue, but I thought I'd throw it out there any way.

That's it!

Once I assigned the field tccom010.txta to a new domain and printed that (cust.ptr) on the report it works!

Thanks for the wonderful help!

Modified reports to print a pointer variable rather than directly from the table. This cleared up some of the problems. Another problem was discovered when more than one text message was being printed where the master tables were logical tables.

There is a solution 120250 that corrects these problems.

Thanks for the help.:)

This is indeed a known problem and related to ttstprepdll

Newer updates have a dependency to the portingset (6.1c.06 at least). Be aware: installing a newer version and not updating the portingset will yield big problems.

When you create your own reports (or objects in general), do not forget to also install the newer $BSE/include6.1 files from solution 114812. Note: on NT rename the *dmp file to *.tar and install using WINZIP.

:rolleyes: