How to implement it though? My thinking process would be to do something like the following ...
1. Create a separate table, calling it something like 'hardware_changes'. Each row would be an entry of a single hardware change to a system. So, the table would probably need to store the table/field of the data that changed, the previous amount the field was at, and the amount it currently had at that audit. The rows could have the system_uuid and timestamp of the audit to make it unique.
2. When the data is submitted to admin_pc_add_2.php, the page would need to grab the data on the system, if it already exists, then it would need to compare whatever field values you want to look for changes in. If there is a change, then it should add that entry to the table mentioned above.
3. A separate view definition would need to be created to show the hardware changes for a specific system.
Maybe there's an easier/more elegant way to do it? I dunno, just my thoughts. Doesn't sound like it would be too daunting to add, though obviously not minor.
_________________ OA Server: Debian Squeeze w/ Apache2 Auditing: 700 Workstations, 250 or so Retail Terminals, about 75 Servers OS's: Windows XP/2003/2008/2008 R2/Vista/7, Debian LDAP: Active Directory 2008 R2
|