Version 4 - remember that! Importing problem.

[Golden Gun]

I have a customer who has Catalog Version 4 for their ecommerce site (year 2000!). They would now like to upgrade to Version 8 to get all the added benefits and functionality.

I am loathe to reinput all their pricing / products if I dont have to so have tried exporting a Snapshot of the old site.

I then did the following with this .acd file.

Imported to V5. Exported snapshot
Imported to V6. Exported snapshot
Imported to V7. Exported snapshot

Up till now everything was working fine.

However when I try to import it into Version 8 (Designer) it corrupts and wont open. I want to import the data and buy a client to make use of my Designer software.

The error message is as follows:

"Failed to insert record with values (40, 'P3PPolicy', 'Content of compact P3P Policy', 0, 7, 0, NULL, 0, 0) in table [Variable] - fatal error.
Reported error was:

The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again."

Anyone know what on earth is going on?

Cheers

Elliot

[pinbrook]

I can't answer the DB issue except to say it might be worth contacting actinic support as they seem quite good at sorting out corrupt DBs on upgrade to 8.

The other solution is to use the flat file export from 4 and import this into 8

[Golden Gun]

Help!

Thanks for your reply, how do you do a flat file export in v4?

I have a new error message now when importing to V8. Anyone know what on earth this means and how i fix it?

Cheers

Elliot

_

"Failed to insert record with values (40, 'P3PPolicy', 'Content of compact P3P Policy', 0, 7, 0, NULL, 0, 0) in table [Variable] - fatal error.
Reported error was:

The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship. Change the data in the field or fields that contain duplicate data, remove the index, or redefine the index to permit duplicate entries and try again."

[RuralWeb]

The changes you requested to the table were not successful because they would create duplicate values in the index, primary key, or relationship

This seems to occur if you are using user defined reference numbers and they are too long.

[Golden Gun]

is this easy to correct? How do you do this?

[Toby B]

I think the DB is corrupted from all the upgrades. Can you log a support request so we can fix the V7 snapshot?

http://www.actinic.co.uk/support/register.htm