Best practices for updating data base
January's SQL Slammer worm reminded us of the importance of patching vulnerabilities in computer software.
Most successful computer attacks exploit well-known vulnerabilities, for which patches exist.
The problem is that hundreds of patches are released each month, many of which apply to OSes and applications residing in your organization's network.
How do you know which patches to install, and which to ignore?
If you've just added a record you will likely get a syntax error in the Where clause on the form open but that's easy to locate and figure out.
What is particularly of concern though is that occasionally you have some field level validation such as a required field or a foreign key which hasn't been entered but defaults to 0. Should I misspell the variable name, then once I hit the space bar, and the VBA editor does not change the case of the variable name from lower to proper case, then I also know I made a typo without waiting to get a compiler error.
I also display this information on the main menu and the About form.
If I have a change in the BE format, ie new tables, fields or indexes I use the BE version number to run some code which does the appropriate updates. So see Date/Time: Return Dates in US #mm/dd/yyyy# format for queries. I also like defining the regional date format on my system as dd/mm/yyyy just to help locate these problems.
Any changes you've made to the data will likely not be displayed on the other forms or reports.Some companies have staff dedicated to managing this process; others use vulnerability reporting services. Assess the vulnerability and likelihood of an attack in your environment.Perhaps some of your servers are vulnerable, but none of them is mission-critical.The smaller the number of versions you have running, the easier your job will be later.Step 3: Make a list of all the security controls you have in place--routers, firewalls, IDSes, AV, etc.--as well as their configurations.Access will happily close the form and *NOT* save the record. The explicit save of the record will generate an error message for the user allowing the users to correct the data. For DAO I very much prefer to use where str Command is the SQL statement, lng Records Affected is a Long variable in which ADO returns the number of records affected, and ad Cmd Text identifies str Command as a text command rather than, for example, the name of a table, view, or stored procedure.