RecordDeletedLog

The table gets populated by triggers which record, as you have noted, kind of useless information, as who would know what the "item id" corresponds to.

In theory, you could alter the recorddeletedlog table and add a couple of columns such as itemlookupcode and itemdescription. You would have to re-create the trigger (drop it first, then recreate it) so that it also populates the deleted item's itemlookupcode and description.

First implement the built-in security if you haven't already done so, to limit who can delete what. Triggers aren't for the faint of heart, it does require some SQL knowledge to alter the table, drop the trigger, and recreate it to also populate the added columns.

H> This table doesn't get you much information about what is deleted? What can

Thanks convoluted

Have played with triggers before and you are correct to say that sometimes they don't give the desired affect . So test well - on a test machine first. What I was wondering why Microsoft did this useless table maybe I was missing something. Agree with you that ILC, description and cashier name should be included. What are other users doing... Once my new trigger is created I will share and ask for comments. - open source style.

Danny

Dan, I imagine the Recrod Deleted Log was not a device of Microsoft but of SMS, who originally wrote RMS (QuickSell). And I certainly agree with you that it is not great, but it is better than nothing, at least you know _something_ was deleted. This has actually helped us track a few problems for customers, as simple as it is. As far as it never being flushed out to be more useful, I imagine it, like some many other things in RMS, were a good idea that Micorsoft just chose not to run with.