MSDE Database Issue

Posted by Brad_TOB on February 9, 2007, 5:34 pm

Please log in for more thread options

We have an issue that's come up with our RMS database. Everything works fine,
except when to try and add a series of new items as a part of a matrix. The
items are created without a hitch (you can even look them up by individual
UPC) but when you inspect the newly-created matrix, other items from other
matrices are randomly thrown in place of the correct items that we just
created. No matter what we do, any new item matrix we create is populated
with what seems to be a random selection of existing items.

Now, as a test we created a new database and populated it with data from our
most recent backup (much to our chagrin, December 30th) and everything works
fine. We're probably just going to re-build things from that point but I
figured it was worth asking if anyone has a less complicated solution to our
problem.

Has this ever happened to anyone here? Is there any way we can repair the
existing database? Any help would be greatly appreciated.

Posted by Afshin Alikhani on February 10, 2007, 7:32 am

Please log in for more thread options

You may want to usw our Item Creation Utility as part of our Fashion bundle.
This will give you more capabilities and resolve this reported issue.

Afshin Alikhani - [ afshin@retailrealm.co.uk ]
CEO - Retail Realm
= = = = = = = = = = = = =

> We have an issue that's come up with our RMS database. Everything works

> fine,

> except when to try and add a series of new items as a part of a matrix.

> The

> items are created without a hitch (you can even look them up by individual

> UPC) but when you inspect the newly-created matrix, other items from other

> matrices are randomly thrown in place of the correct items that we just

> created. No matter what we do, any new item matrix we create is populated

> with what seems to be a random selection of existing items.

> Now, as a test we created a new database and populated it with data from

> our

> most recent backup (much to our chagrin, December 30th) and everything

> works

> fine. We're probably just going to re-build things from that point but I

> figured it was worth asking if anyone has a less complicated solution to

> our

> problem.

> Has this ever happened to anyone here? Is there any way we can repair the

> existing database? Any help would be greatly appreciated.