The product reference you entered was not unique

[cobbler]

I use a four digit numerical product reference, which is incremented by one for each new product.
Catalog (V9.0.5) now tells me that "the product reference you entered was not unique. (Oh yes it was matey) Please enter a unique product reference number" every time I try to add an item to the catalog.

I can get round it by adding a suffix of "a" at the end, but it's still annoying. (Strangely an angry set of 9999999999999's also work!)
I've tried compacting the database with no effect.

Has anyone else seen this please? Any suggestions gratefully received as always.

[Duncan Rounding]

Try exporting the catalog and opening it in Excel, then do a search to see if you can find it.

- Do you have any products marked for deletion that could have the same number?

[cobbler]

Thanks for the quick reply Duncan.
I do have a few items for deletion but all definitely have unique numbers. (I used to mail out paper catalogues and all items are created elsewhere before going in to Catalog. Occasional errors with cat numbers are made, but any duplicates would be picked up before they get that far.) At first I thought I'd made a tryping error, but it's happening with every item I try to add.
For instance, I enter a ref number of 3441 and "it's not unique etc etc" so I try 3442, 3443, 3444, 3445 all with the same result, but a random number of say 6958 or 99999999 is accepted. As for the export to Excel I have never had any sucess with file exports, they are to all intents and purposes, empty. I only have creaky old Excel 2000, maybe that is not up to date enough?

[leehack]

Have you compacted the database, both the catalog and the shipping?

[cobbler]

Compacted both db's to no effect. (I've also managed to open the csv in Quattro Pro and can find no duplicates in there either.)

[leehack]

Something sounds screwed then im afraid, i think you'll need to register a query with support on the actinic site if you don't have cover.

[cobbler]

That would be the next logical step, I was just hoping someone might have come across it before.
I have cover and I already have a snapshot with support regarding another unrelated matter and although I've been told on two separate occasions I would get an update on the situation all I've heard so far is the sound of tumbleweed blowing.....

If I get a resolution to this I'll post it here.

[leehack]

There's a few instances of it mentioned on the forum, but a database compact seems to have solved it and it was on v7 as i recall, so quite sometime ago.

[cobbler]

As you say Lee, I found this before I posted but it's V7, dated 2005, and a compact of the db sems to have cured it:
http://community.actinic.com/showthread.php?t=13504

I'll contact support and wait