I was doing test restores on the new sql version and have come across something dead weird.
I backed up our original db and then tried to restore the database.
On the sale shipment header table i got the error
The sales shipment header table contains a field with a code or text value that is too large for the SQL server type:
Record N.='SPS/00008'
Field Ship-to-address= 'C/O Birkart Int. Forwarders Ltd'
SQL type VARCHAR(30)
I looked in the orignal database and the field type is text 30 and the contents are 'C/O Birkart Int. Forwarders Ltd'
BUT THE WEIRD THING IS IN
C/O Birkart Int. Forwarders Ltd
There are 31 !!! characters. The table has stored 31 Characters in a 30 Character field !!!
One of the characters must be being ignored i would guess at the . or the /
any one seen this before ???
Bruce
0
Comments
But I would be curious to see what happen if you change the '.' and the '/' by any letter from A-Z
Let us know what were the result of your experimentation ...
tarek_demiati@ureach.com
Bruce
command doesn't give an error when you move to a field of
a different length in 2.5. A shipping code of 8 is comming in
with 9 characters. The From length is 9, the to length is 8.
Well that's a relief.. I was beginning t think that I was the only one this would / had happened to.
It would be nice if someone form Navision would comment on this...
Bruce
We found that while localizing NF2.50
One string in acounting period name had 11 chars while NF (c/server)claimed the field lengtht is 10!
Amazingly it is working fine on C/Server! (was working in previous versions for very long time ;-))
But.. after making backup from c./server just to restore it to MS SQL we found it is impossible to import this backup (MS SQL creates it's table fields according to c/server schema i.e. 10 characters, then it is impossible to put 11 chars in it).
BTW: We found nothing dangerous about this "feature". All you have to do is to extend field name in c/server then make a backup.
That is it.
cheers
Krzysiek
nspl