Error "TableData 0 does not exist" during

lagersjeflagersjef Member Posts: 57
Hi,

I am getting the error above when running a database test on 3.70 - only checking database field relationships. This causes the test to terminate and I can't seem to figure out why I am getting this error.

I have seen other posts on the forum that get the same error message for different tables. In those cases I can temporarily create the missing table to fix the problem. However, Navision does not allow creating a table with a number '0'.

Also, I have not figured out from which object this error is occurring. I have compiled all objects in the database and of the compilation errors that occur, I can not find the error "TableData 0 does not exist".

Can anyone help?

Answers

  • Marije_BrummelMarije_Brummel Member, Moderators Design Patterns Posts: 4,262
    There probably is a field with tablerelation = 0

    Export all tables to a textfile and look for the string 'Tablerelation=0'
  • lagersjeflagersjef Member Posts: 57
    Thanks for the super-fast reply.

    I searched through the entire exported table text file for 'tablerelation=0', 'tablerelation = 0', 'tablerelation=''', 'tablerelation=""', etc, but I couldn't find any matches...
  • Marije_BrummelMarije_Brummel Member, Moderators Design Patterns Posts: 4,262
    Sorry,

    I did a little test and Navision exports
    TableRelation=Table0
    
  • lagersjeflagersjef Member Posts: 57
    Cheers!

    I found a few of those instances. I will make some changes, run the test again and post the result.

    Thanks for your help Mark!
  • KowaKowa Member Posts: 925
    Usually the "TableData 0 does not exist" message is displayed when a record
    variable was created ( with or without name) and no subtype was selected. Maybe some further code errors prevent this message from being displayed when the object is compiled.
    Kai Kowalewski
  • lagersjeflagersjef Member Posts: 57
    I think Table0 was a placeholder for a tablerelation that was to be set in an add-on module. But somehow it never got set.

    Anyways, removing these instances fixed the problem. Thanks for your help!
Sign In or Register to comment.