|
Posted by Glenn Adams [MVP - Retail Mgmt on October 4, 2006, 12:11 pm
Please log in for more thread options The impact would be that all of your transaction history at the store
would be shot. All of that is linked to Item.ID. If you delete then
use a 250 to resend all items, you will be generating all new IDs and
none of the existing transaction entries will match them. Also, you
would need to clear out more than just the item table - SupplierList,
Alias, ItemClass & ItemClassComponent would all have to be cleared as
well - those are just the ones off the top of my head, there are
probably a few more...
I think that a better solution would be to export a new DB for that
store from HQ. Make sure that you have requested all Journals from the
store if you want them to be available after the export. Since all of
the duplicates share a common HQID, you should end up with all of the
history linked to a single instance of the item upon export. You should
also test this solution before implementing, but it should be pretty
easy to do.
Glenn Adams
Tiber Creek Consulting
http://www.tibercreek.com glenn@tibercreek.com
----------------------------------------------
Please DO NOT respond to me directly but post all responses here in the
newsgroup so that all can share the information.
Anthony Laidler wrote:
> Was not planning to do it, just wanted to know if anyone has done this and
> what impacts it would have.
>
> "Jeff" wrote:
>
>> Anthony,
>>
>> Sounds like you have some database corruption! Were they really able to
complete a Check without issues?
>>
>> To reduce it from happening again, if running MSDE, follow the directions in
this KB;
>> http://tinyurl.com/or8kx
>>
>> This solved some of my clients with the exact same problem (all running HQ
too!) of duplicated items in the database. The only problem is that you have
the delete the duplicated items manually, one at a time, because there is
nothing unique about the duped item. Do it on the SO and HQ databases, really
anything that is running MSDE!
>>
>> I wouldn't do what you are describing without have a couple of backups and
have tested it _real_ well!
>>
>>
>>
>> --
>> *
>> Get Secure! - www.microsoft.com/security
>>
>> You must be using Outlook Express or some other type of newsgroup reader to
>> see and download the file attachment. If you are not using a reader, follow
>> the link below to setup Outlook Express. Click on "Open with newsreader"
>> under the MS Retail Management System on the right.
>>
>> http://tinyurl.com/75bgz
>>
>> **********
>>
>> A question was asked of me so I am posting it here...What would happen if I
>> was to run an SQL Query and delete all the Items at the store level, and
>> follow it up with a 250 to send everything back to the store?
>>
>> The problem that he is having is that he is seeing some items in the store
>> that may exist like with the same Item lookup number 50 plus times. Of
course
>> I tried to run a Check and ReIndex and it had no effect. I tried to delete
>> just that itemlookupcode and it gives an Overflow Error. The way I was able
>> to delete one of the items was to run the Inventory Wizard and make that
item
>> inactive, and then excuted a SQL query to delete all inactive and that got
>> rid of it since there was no other inactive items.
>>
>> There is a KB on the CustomerSource that I sent him, that relates to
>> duplicates but it did not work for him in this case, and looking at his
>> database, he has several items this way. One item there has the same item
>> lookup like 200+ times. When I look at the database, it has all the same
>> info, store id, HQID, price, cost, everything is identical.
>>
>> Thoughts???
|