I am trying to recreate a Navision object (a form), and it compiles and runs fine. However, if I try to design it again, the following error message occurs; “The type ‘8629’ was not defined for the function”. Any ideas?
Are you doing a retrograde, eg taking an Attain 3.00 object and moving it to 2.60? If so, then the object you are converting uses a function that does not xist in the earlier version. The solution is to remove the call to the particular function on the new version, before you export the text object. _________________________ David Singleton Navision Consultant since 1991 email@example.com___________
Unfortunately Ralph that doesn’t work. By the way David, it was your one of your objects (for maintaining objects within Navision) that I had the problem with. It had something to do with the 2 menu buttons - i copied them from the version 2.60 and pasted them into the version 2 form. The strange thing was the form compiled. Anyway it’s OK now. All I did was to create the menu buttons instead of copying them. Thanks to you both for your replies. Regards
Interestingly that object was written in 1.30GB. It was in a file with 20 or so objects, so I just imported them to W1 2.60 then exported this one. _________________________ David Singleton Navision Consultant since 1991 firstname.lastname@example.org___________
My experience is that .fobs are not very backward compatible (V1.2 won’t read a V2.6 .fob), however they seem to be fully forward compatible. Text format exports, while physically compatible in both directions, force you to make any compatility changes (forward or backward) manually with text edits (such as allowing for the multilanguage feature). Dave Studebaker email@example.com Liberty Grove Software A Navision Services Partner