Wasted a day on this very frustrating error

windrebel

I am getting this error:
The Specified table (Table A) Is different from the table the form uses (Table
I get this when I try to do a table relation to another table using a field in my Main Table (Table C) there are no defined relationships in the (Main table) that has the field that is being referenced. I have added fields and set up new table relationships I still get this error. I have rolled back the table to previous version. Does anyone know of or have they seen this error in any shape or form and what is the fix!!!. No Code runs that I can trace as well as no trigger.
Simpler description I add a field to a table , setup a relation to another table, and no matter what i setup I get this error. HELP! 1 day gone! ](*,)

DaveT

I would suspect that the error is not related to the new field but the form associated with the related table. Check the lookup form id on the related table. Alternatively are you using a lookup form on the field?

bbrown

Take a look at the LookupFormID or DrillDownFormID of the tables. You will get this error if they reference a form that uses a different table.

windrebel

Thanks I am going to try this in the morning it possibly is the table forms assigned. I did not check this! LookupformID and DrilldownFormID

I'll keep you posted!

#-o

girish.joshi

Bbrown's right. This usually happens when a table is created through cut, paste, and renumber.

windrebel

I took out the table lookup forms and have the same problem unfortunately this is a bastardized file from two development environments I think I have to create this table from scratch.

windrebel

I started to create a new table and a new form I still get this same error with no reference to any lookups or drilldown links.

bbrown

The issue may not be with that table. Look at tables that are referenced by field - table relations of this table.

DaveT

Have you tried to run the related table from the object designer directly to see if you get the error there.

windrebel

Is there any type of relationship restriction or limitation since no matter what I do to create a new lookup it does not work. I cant even debug it since nothing comes up in the debugger. If I put a Table relationship from the field to any existing table it works. I deleted my new table and recreated it fomr scratch still does the same thing. This is Navision 101 What's Up I seem to be losing my grip here! All I can think of is that I have reached some sort of table lookup limitation ??? Any ideas are welcome.

DaveT

Can you export it to text and post it up and I'll have a look

DaveT

Looking at this again as BBrown says I don't think its the new table but the table you're looking up i.e. if the field looks up the item table then Nav opens the item table and displays the list using the form specified in the LookupFormID. The only way I can recreate this error is to relate the field to a table that has a LookupformID who sourcetable is different to the table.

ara3n

Make sure you don't have any local variable in the onlookup trigger.
Also make sure there is no code onlookup.

DenSter

The last time I had that error was when I had to renumber some objects. Say you have table 70000 and form 70000. You renumber the table to 50000. Now you get the error mentioned above, and you can't even open the form in design mode. If part of what you did involved renumbering a table, then you need to make a copy of the table with the 'old' number, and then you will be able to open the form in design, and point it to the right table.