401 worksheet timing out - can I override the upload?

I recently made a number of changes to the description fields in the Item table in my RMS Store Operations database. This change affected about 80,000 items.

Now when I run a 401: Request Data Upload worksheet, the worksheet times out.

I've bumped up the registry setting (HKEY_LOCAL_MACHINE\ Software\ Microsoft\ Retail Management System\ Headquarters\ Client\ Timeout\ Message) from the default 3600 to 3 times that value (10800). It still craps out after

30 minutes or so.

Is there some way that I can manually "trick" the RMS Item table into thinking it has been uploaded, so I don't keep getting stuck? Do I need to do something with the LastUpdated field or the DBTimeStamp field?

I've already manually made these changes in my RMS Headquarters database, so I really don't need it to be updated.

This is what I get for doing such a large update. I should have known from experinece that if I update more than 5000 item records at a time, it will puke.

Reply to
Bill Yater
Loading thread data ...

The field DBTimeStamp is used by the system to find the records modified on database.

You cannot change the value of DBTimeStamp.. it's managed by sql server.

Change in your HQ table the LastUpdated field

cod

Reply to
cod

Changing the LastUpdated field in Headquarters.Item did the trick. I'll have to remember that whenever I do a T-SQL update from now on.

Reply to
Bill Yater

UPDATE ItemDynamic SET SnapshotTime = GETDATE() WHERE StoreID = (SELECT ID FROM Store WHERE Code = 'YOURSTORECODE')

Reply to
cod

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.