|
Posted by Craig on September 3, 2008, 3:58 pm
Please log in for more thread options
Ditto, an inactive feature for cashiers and reps seems like a no brainer.
Craig
> Been wishing for a feature to make employees 'inactive' for a while now.
> In the meantime I use a system like you, I had a 9 prefix to the cashier
> or sales rep number so I can filter them out in reports.
>
> Maybe someday .....
>
> Marc
>
>
>>I agree with that...
>>
>> I've basically set up security so that no one but me can delete _any_
>> records... This all started with cashiers, as if you delete a cashier
>> today,
>> and run a report 6 months from now, you will have no idea what name was
>> associated with that cashier. So while items are a different situation,
>> delete is still a BAD function. At least with cashiers I can put an "XX"
>> in
>> front of the name and change the password to a long garbage string...
>>
>>
>> "David" wrote:
>>
>>> I feel the delete button has done and will continue to do much damage to
>>> the
>>> RMS database especially when an item has history. Can MS amend this
>>> function
>>> such that if an item has history, then it cannot be deleted but instead
>>> suggest to make it inactive? I have come across so many clients with
>>> questions why they see orphaned records in their databases yet they
>>> would
>>> have deleted the items and also some create the exact item lookupcode to
>>> try
>>> retrieve the records but that does not work as it will be a different
>>> record
>>> altogether in SQL.
>>>
>>> Also I may be wrong but don't certain countries/laws prohibit the
>>> deletion
>>> of records before a certain period is up? I heard this somewhere in the
>>> accounting circles...
>>>
>>> my 2c
>>>
>>> David
>>>
>>>
>
>
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML Sitemap