SQL Server Error while importing fob

jorgito

Hi all.

We recently received Navision 4 SP1 and we have merged the custom modifications with SP1 functionality. We created a final fob that contains all the functionality of SP1 along with the custom modifications made for the customer.

When we try to import tha fob into the live database of the customer, we get the following error.

The following SQL Server error(s) occurred while accessing the Item Ledger Entry table: ???103.

Any idea what that means?

Thanx
Jorgito

ara3n

I know that Navision in SP1 has changed the key structure in item ledger entry for better performance. This may have something to do with it.

I would do a Navision backup. Create a local fdb and restore the backup. Load/import the improvements. Do another back of the local fdb with new objects and create a new db and restore the backup.

jorgito

I am sorry ara3n.

I did not completely understand.

Could you be more specific?

What do you mean by improvements? New objects?

I only have one fob that contains everything.

Jorgito

DenSter

The 4.0 SP1 version is not just objects. You also need to make sure that the executables are updated (this is less relevant for SQL Server, but I recommend doing this nonetheless), and that the database is a 4.0 SP1 database, before you can import SP1 objects. It is possible to convert the database by opening the 4.0 database with 4.0 SP1 executables, but the right way to go about is to create a new database with 4.0 SP1 executables, and restore the 'old' database into it, which should take care of all your keys. Then it should also be possible to import new objects without getting errors.

kriki

ara3n wrote:

I would do a Navision backup. Create a local fdb and restore the backup. Load/import the improvements. Do another back of the local fdb with new objects and create a new db and restore the backup.

Maybe easier : delete all secondary keys in the original DB, then import the new objects.

jorgito wrote:

What do you mean by improvements? New objects?

No, ara3n means that the fields in the indexes in existing tables have changed. So there are no new objects.