Computer Architects

Computer Architects

CK 2005/146020/23

<% '******************************************************* '* ASP 101 Sample Code - http://www.asp101.com/ * '* * '* This code is made available as a service to our * '* visitors and is provided strictly for the * '* purpose of illustration. * '* * '* http://www.asp101.com/samples/license.asp * '* * '* Please direct all inquiries to webmaster@asp101.com * '******************************************************* %> <%= RetrieveAndIncrementCount() %> <% ' I placed this in a function so I wouldn't have to worry about ' any namespace collisions. For example... if this was inline ' code and someone named a variable strSQL in a file this file ' gets included into you'd get an error. This way you don't and ' there's no chance of the variables overwriting one another! Function RetrieveAndIncrementCount() ' From adovbs.inc: Const adOpenKeyset = 1 Const adLockPessimistic = 2 Const adCmdText = &H0001 ' Local variables Dim strFilename Dim strSQL Dim rsCounter Dim iCount ' Get filename and build SQL query strFilename = Request.ServerVariables("SCRIPT_NAME") strSQL = "SELECT page_name, hit_count FROM hit_count WHERE page_name='" & strFilename & "';" ' Open our recordset Set rsCounter = Server.CreateObject("ADODB.Recordset") ' Access version: 'rsCounter.Open strSQL, _ ' "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & Server.MapPath("counter_db.mdb") & ";", _ ' adOpenKeyset, adLockPessimistic, adCmdText ' SQL Server version: rsCounter.Open strSQL, "Provider=SQLOLEDB;Data Source=10.2.1.214;" _ & "Initial Catalog=samples;User Id=samples;Password=password;" _ & "Connect Timeout=15;Network Library=dbmssocn;", _ adOpenKeyset, adLockPessimistic, adCmdText ' If we've got a record then we read the current value ' If we don't then we create one, set the filename, and start at 0 If rsCounter.EOF Then rsCounter.AddNew iCount = 0 rsCounter.Fields("page_name").Value = strFilename Else rsCounter.MoveFirst iCount = rsCounter.Fields("hit_count").Value End If ' Increment the count and update the DB rsCounter.Fields("hit_count").Value = iCount + 1 rsCounter.Update ' Close our connection rsCounter.Close Set rsCounter = Nothing ' Return the count (pre-incrementation). RetrieveAndIncrementCount = iCount End Function %>

Your Efficiency is MY Challenge!!

Supported Initiatives

Home

About Us

Contact Us

Service List

Disaster Recovery

Backups

Tape Backups

CD / DVD Backups

Disk Backups

On-Line Backups

Health Checks

SLA's

Policy Documents

Networks

Upgrades

SPECIALS!!

Internet Services

Project List

Promo Product List

Documents, and more documents, and then there are Policies!

Documentation to improve your audit score!

Policy Documents are here to stay and must be part of your housekeeping, especially the I.T. department.

Policies are an integral part of your company infrastructure and should be treated as such. I.T. Policies are “living” documents and while this makes this an onerous task of keeping the information up to date, it is absolutely vital that is. The next time you have a computer crash of theft and your documentation is not up to date, you will be down for a lot longer than anticipated, normally to the detriment of the company.

All International companies have stringent audit policies and these  include the Sarbanes-Oxley guidelines. These companies normally also get yearly visits from local appointed auditors as well as bi-annual visits from the holding company auditors.

Once these policies are in place and maintained, your company will be able to overcome any catastrophe. I can hear some of you saying, “I do not need policies, my IT guru has everything in his head”. Quite rightly so, however what about the “bus” factor? Tomorrow he steps out into the street and a bus runs him over. Now you are in a situation where your guru is gone, everything was in his head or some sophisticated filing system that no-one else can decipher, and you sit with trying to get your business back up and running in the shortest time possible; time is money so get the policies into place to protect your business!

There are quite a few different policies available, see the list on the left, but your priority must be a Disaster Recovery Plan. Then depending on the size of your business and confidentiality required, a Systems Security and or Electronic Systems Usage policy. These will cover the majority of your business segment and will get you a high score in the next audit.

 

· Disaster Recovery Plan.

· Systems Security.

· Internet Security.

· Electronic Systems Usage

Policy Documentation; the KEY to your business future!

Andy van Eyk

Mobile: 082-571-2751

Fax: 086-688-6827

E-mail: andy@comparch.co.za

To contact us:

Policy Documents