Modification of table 27

h-d.neuenfeldt · November 5, 2003, 3:45pm

Hi,

my NSC won’t do it for me :

System : Navision 2.01

Wish : I would send you the fob with only table27 in
You delete in the fob fieldno.26
you send me the fob back.

I need this modified fob for testing and my licence don’t let me do it.

Nelson · November 5, 2003, 3:50pm

Hello, I’m sorry but this would still not work. There would be an attempt to delete the field at the time of import and this would generate the same error message.

h-d.neuenfeldt · November 5, 2003, 4:01pm

even if it is a fob ? From txt i know the effect.

Steffen_Voel · November 5, 2003, 4:01pm

I think it’s more a case of can’t than won’t - even NSC’s can’t delete standardfields - and besides, what would be the point?

h-d.neuenfeldt · November 5, 2003, 4:03pm

I will test where the field is used and what is the purpose of the field. My NSC changed the standard 5 years ago and the developer isn’t anymore so nobody can explain what happend.

Nelson · November 5, 2003, 4:12pm

Yes, Hans, I’m afraid even with a .fob file. The deletion is related to the license file which is used to import.

h-d.neuenfeldt · November 5, 2003, 4:13pm

SH… Any Ideas how to solve the problem ???

Steffen_Voel · November 5, 2003, 4:21pm

Use Impulse Workbench 2. Export all objects to text, then perform a search for the field

Nelson · November 5, 2003, 4:31pm

I have no experience with Impulse Workbench but I saw some reviews somewhere… But I think it is a commercial software, am I right? Steffen Voel’s 2nd option is very easy to execute. One tip: before exporting, rename field 26 from “Average Cost” to something really stupid and out of the ordinary… maybe “!!! I’M GONNA FIND YOU !!!” … It will be easier to follow the references in the text file this way [B)] [:D]

h-d.neuenfeldt · November 5, 2003, 4:37pm

Nice trick, i will do so …

EBloom · November 5, 2003, 5:54pm

Hello, It is not possible, either for a Navision customer or for an NSC to delete standard Navision fields (i.e. Those below 50000), regardless of whether they are used or not. You cannot change this either in the designer or as a text file, as Navision will reject the text file on import (“You do not have permission to delete field no. XXX”). If you are doing this so that you can create new fields because you have reached the permitted record width limit for 2.01, then the only solution is to delete some of your own old fields (>50000) to increase space or upgrade your executables to 2.50 or higher, which allow wider record widths. Hopefully this will clarify things.