|
Home > Articles
ASP Scripts to Determine if Specified File and Folders Exist
Here are two VBScript functions that check to see if a specified file or
folder exist on the server. As such they can be used to improve error handling on ASP
pages that read or write files from disk.
Checking to see if a File Exists
The first function (CheckFileExists) checks to see if a file
exists. It returns 'True' if the file exists, or 'False' if it does not.
<%
Function CheckFileExists(sFileName)
Dim FileSystemObject
Set FileSystemObject = Server.CreateObject("Scripting.FileSystemObject")
If (FileSystemObject.FileExists(sFileName)) Then
CheckFileExists = True
Else
CheckFileExists = False
End If
Set FileSystemObject = Nothing
End Function
%>
The following code is an example of how to use the function:
<%
If CheckFileExists("D:\ProductionReports\July2005\July-12-2005.xls") Then
Response.Write("The production report for July 2005 is
available")
Else
Response.Write("The production report for July 2005
cannot be found")
End If
%>
Checking to see if a Folder Exists
The second function (CheckFolderExists) checks to see if a folder
exists. It returns 'True' if the folder exists, or 'False' if it does not.
<%
Function CheckFolderExists(sFolderName)
Dim FileSystemObject
Set FileSystemObject = Server.CreateObject("Scripting.FileSystemObject")
If (FileSystemObject.FolderExists(sFolderName)) Then
CheckFolderExists = True
Else
CheckFolderExists = False
End If
Set FileSystemObject = Nothing
End Function
%>
The following code is an example of how to use the CheckFolderExists
function:
<%
If CheckFolderExists("D:\ProductionReports\July2005") Then
Response.Write("The production reports for July 2005 are
available")
Else
Response.Write("The production reports for July 2005 are
not available")
End If
%>
Problems with File Permissions
A problem with these two functions is the fact that they will check for
the existence of files and folders, but do not indicate whether the user has the
appropriate permissions to view them.
A way around this problem is to use the Permission Checker Component. This
Component is supplied with the Internet Information Server 4.0 Resource Kit, and also with
the Internet Information Services 5.0 of Windows 2000. This object has one method -
HasAccess, which makes it possible to determine if the user has permission to read a
specified file.
An example of using the component is below:
<%
Set PermissionChecker = Server.CreateObject("MSWC.PermissionChecker")
If PermissionChecker.HasAccess("D:\ProductionReports\July2001\July-19-2001.xls") Then
Response.Write("You have permission to view the July
2001 production report")
Else
Response.Write("You do not have permission to view the
July 2001 production report")
End If
Set PermissionChecker = nothing
%>
The Permission Checker Component can also be incorporated into the
original CheckFileExists function:
<%
Function CheckFileExists(sFileName)
Dim FileSystemObject
Set FileSystemObject = Server.CreateObject("Scripting.FileSystemObject")
If (FileSystemObject.FileExists(sFileName)) Then
Set PermissionChecker = Server.CreateObject("MSWC.PermissionChecker")
If PermissionChecker.HasAccess(sFileName) Then
CheckFileExists = True
End If
Set PermissionChecker = nothing
Else
CheckFileExists = False
End If
Set FileSystemObject = Nothing
End Function
%>
The function can then be used in a similar way to before:
<%
If CheckFileExists("D:\ProductionReports\July2001\July-12-2001.xls") Then
Response.Write("The production report for July 2001 is
available")
Else
Response.Write("The production report for July 2001
cannot be found or you do not have permission to view it")
End If
%>
Further Reading
Useful Development Tools
| ASP
Documentation Tool™ |
| Automatically creates developer documentation for ASP 2.0
and 3.0 web applications written in VBScript and JScript. Documentation for Microsoft
Access, SQL Server 7/2000 databases and Visual Basic 6.0 components associated with the
web application can also be incorporated into the reports. Documentation is created in
HTML, HTML Help and plain text formats. |
 View Sample
Output (HTML Help format).
 View Sample Output (HTML Format).
 Download
Trial Version (5.2Mb ZIP file). |
| .NET Documentation Tool |
| Automatically creates technical documentation for .NET Framework Windows and ASP.NET applications written in C# or VB.NET and SQL Server 7/2000/2005 or Microsoft Access databases associated with the
application. Documentation is created in HTML, HTML Help and plain text formats. |
View Sample
Output (HTML Help format).
View Sample Output (HTML Format).
Download
Trial Version (5Mb ZIP file). |
| SQL
Documentation Tool |
| The SQL Documentation Tool creates technical documentation for Microsoft SQL Server 7.0 and 2000 databases. Technical documentation is created in HTML and HTML Help formats. The HTML Help format documentation is fully searchable and cross referenced. The SQL Documentation Tool documents SQL Server Tables, Views, Stored Procedures, Triggers and Table Relationships. |
View Sample
Output (HTML Help format).
View Sample Output (HTML Format).
Download
Trial Version (10.3Mb ZIP file). |
| Indexing Service Companion |
|
The Indexing Service Companion is a Windows application that extends the functionality of the Microsoft Windows Indexing Service so that it is able to index content from remote websites and also from ODBC databases. As such it can be used as a low cost alternative to Sharepoint Portal Search Services.
|
Try Sample Search Facility.
Download
Trial Version (1.7Mb ZIP file). |
| The Website Utility |
| The Website Utility examines websites for errors and
areas that need to be optimised for search engines by using a built in web crawling engine.
Errors checked for include broken or moved hyperlinks, missing page titles and missing meta tags.
It also generates HTML for use in creating website site maps (table of contents pages - like this one), and is
able to create both client-side JavaScript Search Engines and server-side ASP Search Engines for a website. |
View Sample Output (HTML Format).
Download
Trial Version (3Mb ZIP file). |
|
