I had Generated New Custz Maintain Session where prog. script is empty. While inserting records I am getting error msg as

1 : Fatal Error : Use of NULL pointer on ' '
2 : Fatal Error : Cannot continue in tdpur0002m819 in DLL:ottstpstan

Please help me.

Thanx

Required URGENT HELP !!!!!!!

Ganesh,

Is your table is a customised table if yes, then paste the structure of table with domains and also mention at which field you are receiving the error message.

I had Generated New Custz Maintain Session where prog. script is empty. While inserting records I am getting error msg as

1 : Fatal Error : Use of NULL pointer on ' '
2 : Fatal Error : Cannot continue in tdpur0002m819 in DLL:ottstpstan

Please help me.

Thanx

Hello,

generate session with script:

declaration:
table txxyyyzzz


Regards

A session should either use the standard script, or have the own script declared. If you use specific script, of course it cannot be an empty script...

script is not empty, it contains code as:

declaration:
table ttdptl020 | Godawan Inventory Transactions
table ttiitm001 | Items

Hi Manoj

plz see the attachment for custz. table structure used in the script. I am getting error msg at item field.

Thanx

Hi Ganesh,

I think the problem is due to texa field in your customised table coz you have set the reference of texa field with tttxt001 and while inserting the record in your customised table, the initial value is zero and that may be not existing in tttxt001.

Hi Manoj

I had checked the table tttxt001 and observed there is no record of value zero but I think this is not the probs. Plz see the attachment to check where is the error message.

Thanx

Did you compile the script? Does it compile without errors/warnings?

Do you have any checks for the field item in the script? (check.input ...)
If no, because you don't have any reference to item in your table it looks like a corrupted DD to me.
Did you have a reference before?

Regards
csecgn

Hi En

I had compiled the script without error / warn messages.

Hi csecgn

There is no field checks used in the script and as there is possibility of reference of item field with table tiitm001 and afterwards it may be cancelled and ran CRDD. If DD is corrupted then how to overcome this probs ?

Do you have any checks for the field item in the script? (check.input ...)
If no, because you don't have any reference to item in your table it looks like a corrupted DD to me.
Did you have a reference before?
Thanx

In Baan IV with Solaris some things don't work like expected, so I only can tell you my way:

Add the reference to the item field
Save the table structure
remove the reference again

Check the table ttaad502, Company 000 for following entrys:

tiitm001
your table

If this entrys are there, all is OK and you can can convert the table. IMHO you do don't need to mark reconfigure, because there is nothing to reconfigure for him.

I prefer the convert for all tables (because of references).

I use Covnert to runtime dd (ttadv5215s000, started directly from Maintain table definitions)

If this doesn't help, then you have to add the reference, reconfigure, remove the reference and reconfigure again. Sometimes it needs the complicate way.
(and check for every step that your tables are in the ttaad502. Only tables in this table will be converted)

Take care that in the ttaad502 only tables you really want to reconfigure and check also ttaad501, ttaad503 for "dangerous" entrys (tdsls050, tdsls051...)!

Hope this helps

Regards
csecgn

Hi Ganesh,

Drop your customised table and re-create again or delete field item from form and dump the form and again put item on form.

Its just a thought.

Hi csecgn

Probs solved after followed your second method. Thanx for the same.


In Baan IV with Solaris some things don't work like expected, so I only can tell you my way:

Add the reference to the item field
Save the table structure
remove the reference again

Check the table ttaad502, Company 000 for following entrys:

tiitm001
your table

If this entrys are there, all is OK and you can can convert the table. IMHO you do don't need to mark reconfigure, because there is nothing to reconfigure for him.

I prefer the convert for all tables (because of references).

I use Covnert to runtime dd (ttadv5215s000, started directly from Maintain table definitions)

If this doesn't help, then you have to add the reference, reconfigure, remove the reference and reconfigure again. Sometimes it needs the complicate way.
(and check for every step that your tables are in the ttaad502. Only tables in this table will be converted)

Take care that in the ttaad502 only tables you really want to reconfigure and check also ttaad501, ttaad503 for "dangerous" entrys (tdsls050, tdsls051...)!