günther
21st November 2002, 16:06
Our users have been complaining about the above error for about two years now. We reported the problem to baan, but they cannot find the problem because it happens only sporadically.

I would like to know if anybody else gets an appropriate message on the third step within tipcf5280m000 (generate sales order structure) after the device has been selected and the user presses "continue":

Fatal error : Use of NULL pointer on ''
Fatal error : Can not continue in tipcf5280m000 (choice.report)

Btw.: no customizations here, system up-to-date, Baan IVc4

Regards

Flip_J
21st November 2002, 16:44
Found one Case 544532 but it could be yours.

Solution:
If your Current VRC is:
B40_c, B40_c1, B40_c2, B40_c3, B40_c4:
/ftpdownload/updates/B40_c/152062stnd

günther
21st November 2002, 17:05
Thanks Flip_J,

but that was our case.

EdHubbard
30th November 2002, 00:23
We used to get this error sporadically on our 4c3 system which we upgraded to 4c4 from in June this year.

It seemed to happen most often with :

1. A feature which we changed sequence number for
2. Feature options that had been added more recently.

I could find no technical reason why - data type was correct domain etc. and we installed numerous patches but it didn't ever get fixed - and without pmc related sessions were never properly updated in tandem.

With 4c4 (SP9) we have never had this error!

What did help once or twice on our 4c3 system was to reorg. table tipcf520 as the error message implies a table index issue - just make sure you back it up first!

ssbaan
2nd December 2002, 18:26
WE ran accross this problem a long time ago using 4c2 and
also had it occur in some of our personalizations. According to
BaaN (at the time) a 'Null pointer error', meant that you have some reference in a table to another table, and one of the tables
have not been converted to runtime properly. doing a create/convert to run time wide open (all packages) seem to solve our problem.

What you could do is check all the references in the tables involved and see if they exist in the data dictionaries of the 'referred' tables.

for example, if the table tdcms030 has a reference to the table tiitm001 on the field item, then the data dictionary for the table tiitm001 should have an entry as below;

:REFC:tdcms030.item 1 t1

(this is the Unix data dictionary ffile where this should appear)


Hope this helps!