Windows Services Frequently Asked Questions (FAQ):

Windows Services Frequently Asked Questions (FAQ): Copyright Hostplus.ca 2005 V1.321 TABLE OF CONTENTS: Introduction to the Hostplus Hybrid System... 4 NT Services on the Hostplus Platform... 4 Hostplus's Hybrid System... 4 Differences between Windows-only hosting and the Hybrid System... 4 Database Support on Hostplus's Platform... 5 DSNs and conventions... 5 Functional Components... 6 Microsoft Access 2000/02/03... 6 Why is MS Access 2000/02/03 software only functional and not optimized on your architecture?... 6 ASP/ColdFusion + MS Access... 7 Why are ASP/ColdFusion + MS Access only functional and not optimized on your architecture?... 7 Components Not Recommended... 8 MS-Access 1997... 8 FrontPage + MS Access... 8 Non-Functional Components... 9 DB Connections from multiple domains... 9 Why are Connections from multiple domains to one specific database not functional on your system?... 9 Custom DLLs... 9 Why are Custom DLLs not functional on your system?... 9 Custom COM Components... 9 Why are custom COM Components not functional on your system?... 9 Created on 11/30 2005-1 -

Custom ColdFusion Tags... 10 Why are Custom ColdFusion tags not allowed on your system?10 Clustered Architecture Compatibility... 11 ASP.NET... 13 ASP.NET Supported and Unsupported File Extensions... 14 ASP.NET CODEBEHIND and DDL File Explanation... 15 Additional ASP.NET information... 15 ColdFusion 5... 18 About ColdFusion 5... 18 ColdFusion Applications... 18 ColdFusion Scripting Language... 18 MS Access Warning Messages... 19 Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access Driver] Cannot update. Database or object is read-only... 19 General Questions... 20 How do I connect to my MSSQL DB?... 20 Why does my site perform better on my local machine?... 24 Possible Causes for Broken Sites... 24 Access DB performance issues... 25 My Access DB site is performing poorly on the clustered architecture. What are the possible reasons/solutions?... 25 Can I use Custom DLL s /Active X components?... 26 Can I use Custom CFM tag s?... 26 Supported Components / tags... 26 What Third-Party Components are currently installed?... 26 Payment Gateways... 27 Which Payment Gateways are installed on the Hybrid Platform?... 27 SSL... 27 How are SSL considerations handled on the Hybrid?... 27 Supported Components/Tags... 28 Which Versions and Supported Components/tags do you support?... 28 Coding Examples... 31 ASP... 31 (ASP) DSN connection for MS Access... 31 (ASP) DSN connection for MS SQL... 31 Solution:... 31 Created on 11/30 2005-2 -

(ASP) DSN connection for MySQL... 31 Solution:... 31 (ASP) DSNless Connection for MS Access... 31 (ASP) DSNless connection for MS SQL... 32 (ASP) DSNless connection for MySQL... 32 (ASP) Defining Paths... 32 Coldfusion... 33 (Coldfusion) DSN connection for MS Access... 33 (Coldfusion) DSN connection for MS SQL... 33 Coldfusion) DSN connection for MySQL... 33 (Coldfusion) DSNless Connection for MS Access... 33 (Coldfusion) DSNless connection for MS SQL... 34 (Coldfusion) DSNless connection for MySQL... 34 (Coldfusion) Defining Paths... 34 ASP.NET... 35 (ASP.NET) DSN connection for MS Access... 35 (ASP.NET) DSN connection for MS SQL... 36 (ASP.NET) DSN connection for MySQL... 37 (ASP.NET) DSNless Connection for MS Access... 38 (ASP.NET) DSNless connection for MS SQL... 39 (ASP.NET) DSNless connection for MySQL... 40 Created on 11/30 2005-3 -

Introduction to the Hostplus Hybrid System NT Services on the Hostplus Platform Hostplus's Microsoft Windows NT hybrid services provide basic ASP, Coldfusion, Access and MSSQL services targeted at the needs of SME's, all at a price point considerably lower than a dedicated NT solution. With the ability to use both UNIX and NT technologies in unison, the Hybrid solution offers a less complicated, more robust, lower cost method for users to employ the most popular NT hosting features. Hostplus's Hybrid System Once a customer has enabled Windows NT services, the hosting system uses file extensions to determine when to send NT-specific requests to NT servers. 1 This is made possible by Hostplus's redundant, distributed architecture. Site content is housed on Network Filers instead of individual web servers; along with removing individual web servers as a point of failure, this allows content for one site to be served through multiple machines. With this system a user can mix Unix and Windows content in the same site. Differences between Windows-only hosting and the Hybrid System Permissions: The entire Hostplus system uses Unix-based permissions, even for Windows content. Stability: Superior redundancy provided by distributed, clustered architecture Case Sensitivity: The Hostplus System is case-sensitive; this can be bypassed using an.htaccess file placed in a user's public directory (syntax =CaseInsensitive ON) Flexibility: Designers can mix Unix and Windows functionality in the same hosting environment Secure: Hostplus's hybrid system uses a streamlined Unix security model. Front Page: The Hybrid Platform handles Front Page extensions on Unix servers. The Hostplus system handles most FrontPage functionality (e.g. 1 Nonspecific requests (such as HTML) will be served by Unix servers;.asp and.cfm requests will be served by Windows 2000 servers. Created on 11/30 2005-4 -

forms, themes); However, direct database integration via the FrontPage interface is currently non functional. DSNs (Data Source Names): Up to two DSNs can be employed. They must follow our prefix_domain_com naming convention. Paths: Local system paths (ie. C:\My Documents) cannot be used since site content is not stored locally Supported Language platforms: HTML, PHP, CGI and PERL are parsed by the UNIX portion of the hybrid. Database Support on Hostplus's Platform The Windows database types supported on the Hybrid platform are Access and MSSQL DSNs and conventions Hybrid system customers can integrate their databases into their websites using either of the following methods: DSN connection method: A DSN is used by applications to request a connection to a system ODBC data source. It specifies the computer name and (optionally) the database that the DSN maps to. To create a DSN for MS Access databases, the.mdb file must exist in the /databases directory of the end-users file structure. DSN-less connection method: Also known as the OLE DB connection method. This method allows greater flexibility for end-users; the database does not have to be located in a specific directory. The database can be located anywhere within a client's directory structure, and can be accessed in their code as long as the proper path is specified. Created on 11/30 2005-5 -

Functional Components Microsoft Access 2000/02/03 Why is MS Access 2000/02 software only functional and not optimized on your architecture? Microsoft Access was designed as a single-user desktop database, and not for server use. MS Access 2000/02/03 is functional on our system and suits web applications well when dealing with small- to medium-size business websites, which deal with a reasonably low level of traffic; however, the functional design limitations of MS Access itself (being a desktop program as opposed to a server program) increases the likelihood of poor performance when large numbers of users make simultaneous calls to the Access database. For these reasons, it is recommended that MS Access be used solely for development purposes and not for production. Recommended Alternative: Although MS-Access 2000/02/03 is functional and works reasonably well on our system in most situations, you may benefit from upgrading to a true multi-user database platform such as MS SQL or MySQL. We have found that sporadic performance issues occur when traffic-intensive sites run on Microsoft Jet and IIS. We have ensured that our system is using the latest Microsoft Jet Components and Updates. We recommend that the native Jet OLE DB provider be used in place of the Access ODBC Driver. Excerpt from Readme.txt (IIS) The following article outlines Microsoft's recommendations to implement an SQL Server Database for use under IIS to accommodate for web, commerce, and transactional applications. http://support.microsoft.com/default.aspx?scid=kb;en-us;q299973 Created on 11/30 2005-6 -

ASP/ColdFusion + MS Access Why are ASP/ColdFusion + MS Access only functional and not optimized on your architecture? MS Access was designed as a single-user desktop database, and not for server use. MS-Access 2000/02/03 is functional on our system and suits web applications well when dealing with small- to medium-size business websites that handle a low level of traffic; however, when used on larger enterprise-type websites with a heavy amount of concurrent users making requests to an MS Access database, unpredictable results may occur. We recommend that MS Access be used solely for development purposes and not for production. Recommended Alternative: Although MS-Access 2000/02/03 is functional on our system, for performance and reliability we strongly recommend the use of MS SQL Server for the deployment of production-quality Web applications. Although Active Server Pages work with any ODBC-compliant database (such as MS Access), it has been extensively tested and is designed to work with Microsoft SQL Server. Although the sample Web site and examples in this release use Microsoft Access, we recommend that MS Access be used solely for development purposes and not for production. The following article outlines Microsoft's recommendations to implement an SQL Server Database for use under IIS to accommodate for web, commerce, and transactional applications. http://support.microsoft.com/default.aspx?scid=kb;en-us;q299973 Created on 11/30 2005-7 -

Components Not Recommended MS-Access 1997 Why is MS-Access 1997 not recommended on your architecture? The latest MDAC (version 2.8), which is currently installed on our system, is not compatible with Access 97 databases. You may find that your database worked originally; however, once you write data to the database it will generate this error. In our clustered hosting environment, our main focus is security. In order for us to provide you with acceptable levels of security, our operating systems must be configured with current service packs and patches. If this is an Access 2000 database, it is likely that is it corrupted. FrontPage + MS Access Why is FrontPage + MS Access not recommended on your system? Our system architecture does not allow you to edit your MS Access database though the FrontPage GUI. Both must be managed separately. Created on 11/30 2005-8 -

Non-Functional Components DB Connections from multiple domains Why are Connections from multiple domains to one specific database not functional on your system? In the best interest of our clients, our platform does not allow actions of one domain to affect the population of other domains residing on our system. Multiple domains to one specific MS Access database are prohibited on our system due to strict system security settings. Recommended Alternative: If this functionality is required, we recommend the use of an MS SQL database. Custom DLLs Why are Custom DLLs not functional on your system? Custom DLLs or ActiveX components are prohibited on the hybrid system. Components that are poorly coded are known to cause server instability, excessive resource consumption and reduced site performance. For this reason these types of proprietary, site-specific applications are much better suited to a dedicated server environment. Custom COM Components Why are custom COM Components not functional on your system? Custom COM components are prohibited on the hybrid system. Components that are poorly coded are known to cause server instability, excessive resource consumption, and reduced site performance. For this reason, these types of proprietary, site-specific applications are much better suited to a dedicated server environment. The following third-party COM components are currently installed: ASP Mail ASP JPEG ASP Upload ASP Encrypt SA-FileUP Created on 11/30 2005-9 -

Jmail CDONTS Soapbox Toolkit 2.0 SP1 SmartMail SmartUpload Custom ColdFusion Tags Why are Custom ColdFusion tags not allowed on your system? Custom CFM tags are prohibited on the hybrid system. Tags that are poorly coded are known to cause server instability, excessive resource consumption, and reduced site performance. For this reason, CFM Tags are much better suited to a dedicated server environment. Created on 11/30 2005-10 -

Windows NT Component/Service Clustered Architecture Compatibility Optimized Functional Not Recommended Not Functional Databases MS-Access 2002/03 MS-Access 2000 MS-Access 1997 MySQL MS-SQL DSN Connections DSN-Less Connections Connections from multiple domains to one specific database on our system. Multiple domain connections do not work with any version of MS-Access. ASP ASP + MS Access ASP + MySQL ASP + MS-SQL Custom DLLs Custom COM Components Cold Fusion Cold Fusion + MS Access Cold Fusion + MySQL Cold Fusion + MS-SQL Custom Cold Fusion Tags MS FrontPage FrontPage + MS Access Created on 11/30 2005-11 -

ASP.NET ASP.net + MS Access ASP.net + MySQL ASP.net + MS-SQL Precompiled DLL s Custom COM Components Created on 11/30 2005-12 -

ASP.NET ASP.NET is a programming framework built on the Common Language Runtime Environment that can be used on a server to build powerful Web applications. By using ASP.NET you can easily write dynamic, high-performance Web applications in record time. ASP.NET offers a number of important advantages over previous Web development models: Easy Programming Model: ASP.NET makes building real-world Web applications easier. ASP.NET server controls enable an HTML-like style of declarative programming that lets you build great pages with far less code than with classic ASP; displaying data, validating user input, and uploading files are all made easy. ASP.NET pages work in all browsers including Netscape, Opera, AOL, and Internet Explorer. Excellent Tool Support: You can harness the full power of ASP.NET using any text editor including Notepad but Visual Studio.NET adds the productivity of Visual Basic-style development to the Web. Now you can visually design (via WYSIWYG editing) ASP.NET Web Forms using familiar drag-and-drop, double-click techniques and benefit from fullfledged code support including statement completion and color-coding. VS.NET also provides integrated support for debugging and deploying ASP.NET Web applications. Rich Class Framework: Application features that were difficult to implement (or required a third-party component) can now be added in just a few lines of code using the.net Framework. The.NET Framework offers over 4500 classes that encapsulate rich functionality like XML, data access, file uploads, regular expressions, image generation, and more. Created on 11/30 2005-13 -

ASP.NET Supported and Unsupported File Extensions Supported ASP.NET file extensions.aspx.asmx Non-Supported ASP.NET file extensions.cs *.csproj.ascx.vb *.ashx.axd.vsdisco.rem.soap.vbproj.webinfo.licx.resx.resources *These file extensions can be used in codebehinds using the src directive. Please note that since they' are critical files, Hostplus has modified its configuration to not return any requests specifically for.cs.vb and.config extensions. A 403 error will be sent instead, but they will still work with windows services. Please note that there may be additional functions/components/extensions that are not supported. If you have any questions in reference to functionality, please contact your Project Manager. web.config and global.asax files DO WORK on the hybrid system. Created on 11/30 2005-14 -

ASP.NET CODEBEHIND and DDL File Explanation The process of separating code from display content is prevalent in most web based languages, and is usually considered good programming practice. With ASP.NET there are two ways to separate and reference code that is located in the code file, from within your asp.net display file (.aspx). The two methods are CODEBEHIND and SRC (Source). The CODEBEHIND method relies on a pre-compiled DLL to be present on the system, which contains all the required code that the ASP page may need. The aspx page will try and reference classes or methods present in the DLL by using the page directive below: CODEBEHIND="mydll.DLL" This method will not work correctly on our systems due to the various security concerns already mentioned. Please note that this also means that code created with Visual Studio.NET will also not function correctly on our systems. This is because Visual Studio.NET automatically uses the CODEBEHIND directive for any ASP.NET page you create with it. Unfortunately there is no way to change this, and so VS.NET generated code will not function. The second option for separating content from code with ASP.NET is the SRC (source) directive. This option uses a source-code file as opposed to a precompiled DLL. The source-code file is a plain text file that contains the actual source code the aspx page will reference. The source file will end with a.cs or.vb extension. The code within the page is referenced using the following page directive: SRC="mysource.cs" This compiles the.cs or.vb source file in a temporary location (not accessible through your webspace) and allows you to reference methods and classes from within this compiled file. To recap, pre-compiled DLL's will not function on our systems; however, you can still separate content from code by using the SRC (source) option and uploading the source file instead of the DLL. Additional ASP.NET information This is a sample web.config file which allows customers to view any ASP.NET syntax errors. To use this script copy the following into a separate file, name the file web.config and upload to the server: <configuration> <system.web> Created on 11/30 2005-15 -

<compilation debug="true"/> <customerrors mode="off"/> </system.web> </configuration> Please note: Customers may notice a delay in the time from when they upload a new version of an existing filename. I.e.: making modifications to their WebForm1.asax file, and overwriting the copy that exists within their webspace. It may take up to seven minutes before this new copy is processed by the.net servers. This is due to an inherent behavior of the.net engine in which compiled assemblies aren t destroyed and recreated quickly enough..net differs from regular ASP on our systems in that we do not need to restart ASP services when a modification to their Global.asax file is made. Again, the same seven-minute interval may be required for these changes to take effect. Created on 11/30 2005-16 -

ColdFusion MX ColdFusion MX provides you with the ability to build and deploy powerful web applications and web services with far less training time and fewer lines of code than ASP or PHP. Some benefits to using ColdFusion include: Easy to use. ColdFusion MX delivers powerful Internet capabilities within an easy-to-learn and highly productive server scripting environment. ColdFusion MX contains: An intuitive tag-based language requiring fewer lines of code by handling low-level programming tasks automatically and simplifying code reuse. A new server-side ActionScript enabling Macromedia Flash developers to use the same scripting language for both client and server logic. Complete support for new ColdFusion MX features within the Dreamweaver MX development environment, including powerful visual layout and prototyping, enhanced code editing and development capabilities, and integrated debugging. Creates a powerful and compelling user experience. ColdFusion MX provides a robust architecture and a rich set of built-in capabilities that deliver high performance and scalability, enhancing your applications with advanced functionality. Fully integrated application services for adding full-text search, dynamic charting, and high-performance connectivity to Macromedia Flash clients to your applications. Innovative architecture that delivers the scalability, reliability, and power of the Java platform without the complexity. Created on 11/30 2005-17 -

ColdFusion 5 About ColdFusion 5 ColdFusion, developed by Allaire, is a complete Web application server for developing and delivering scalable e-business applications. The ColdFusion solution consists of two related packages: ColdFusion Applications ColdFusion Studio: Tightly integrated with ColdFusion Server, ColdFusion Studio provides visual programming, database, and debugging tools for building sophisticated Web applications. ColdFusion Server: ColdFusion Server offers all the runtime services for delivering your e-business applications built on a highly scalable and open architecture. ColdFusion Scripting Language ColdFusion uses a tag-based, server scripting language that is ideal for programming Web applications. Processed entirely on the server, the ColdFusion Markup Language (CFML) cleanly integrates with HTML for user interface and XML for data exchange. Both open and extensible, CFML supports more than 70 server-side tags, 200 functions, and 800 third-party components. In addition, ColdFusion supports Java and C++. Created on 11/30 2005-18 -

MS Access Warning Messages Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access Driver] Cannot update. Database or object is read-only. Please ensure your database has the proper permissions set. Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access Driver] General error Unable to open registry key 'Temporary (volatile) Jet DSN for process 0x4d4 Thread 0x748 DBC 0x84dbc84 Jet'. The process, Thread and DCB numbers may vary Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Microsoft Access Driver] Cannot open database '(unknown)'. It may not be a database that your application recognizes, or the file may be corrupt. The latest MDAC (version 2.7), which is currently installed on our system, is not compatible with Access 97 databases. You may find that your database worked originally; however, once you write data to the database it will throw this error. In our clustered hosting environment, our main focus is security. In order for us to maintain our strict security model, our operating systems must be updated with current service packs and patches. If this is an Access 2000 database, it is likely that is it corrupted. Created on 11/30 2005-19 -

General Questions How do I connect to my MSSQL DB? Connections for administrative purposes can be made via Microsoft s Enterprise Manager 2000. Each database created on the Hostplus system is assigned a unique Database Name, User Name, and Password. These credentials are used whenever a client attempts to make a connection to the database. 1. Start your Enterprise Manager Console, and branch out to the Server group level. 2. At this point you can choose the action menu at the top, and select New SQL Server Registration or right click on your server group and choose the same option. The Register server wizard will start as shown below. 3. Click Next to continue to the next step. Created on 11/30 2005-20 -

4. In the box called Available servers, enter mssql.megasqlservers.com. 5. Click Add." 6. The server name should appear in the Added Servers box. Click Next. 7. At this stage, choose the second authentication mode: The SQL Server Login information that was assigned to be by the system administrator. 8. Click Next. Created on 11/30 2005-21 -

9. Choose a connection option. If you want to login automatically, enter your login name and password in the text boxes provided. Your Login name will be dbm.yourname.com (Substitute your domain name for yourname_com). Your password will be the password you chose with your sales representative. Click Next. Created on 11/30 2005-22 -

10. At this point, the wizard will prompt you to add the newly registered server to your server group. Select the option labeled, Add the SQL Server(s) to an existing SQL Server group. 11. Click Next. 12. At this point, the server registration is completed as shown. Click Finish. 13. You will now have a new server listed in your Enterprise Manager console. You can branch out this server, branch out the databases, and proceed to your database. There you can perform various administrative tasks such as create tables, stored procedures, and more. Created on 11/30 2005-23 -

Why does my site perform better on my local machine? Many factors affect a site's performance on any platform. Usually when a site is under development on an end-user's local machine, the user is viewing static content which is not required to travel via the internet to serve any requests. Possible Causes for Broken Sites My Site Worked fine on a non-hybrid system, now it is broken. What are the possible causes and what can I do to fix these problems? Paths Static paths referenced in client code can cause issues when moving into Hostplus s Hybrid platform. It is not uncommon for end-users to reference absolute file paths in their code ex. C:\My Documents\index.html. Since site content is not stored on local disk, these file path references are invalid. For sites coded in ASP, we suggest using the Server.MapPath method for defining paths. For sites coded in ColdFusion, we suggest using the GetDirectoryFromPath method for defining paths. For more information, please see the coding examples attached below. COM Objects/DLLS/Active X Controls The Hostplus System might not support some COM objects that were utilized on the site from the previous hosting provider. The Hostplus System supports a variety of third-party components that have been thoroughly tested File Permissions UNIX based file permissions work differently than NT based file permissions. The correct UNIX permission settings for.asp or.cfm files is -rw-r--r-- or 644 Naming conventions (Case sensitivity) As mentioned above, the Hostplus System is Case Sensitive. End-users may believe that they are being hosted on an Windows Only base system which are usually Case Insensitive. Created on 11/30 2005-24 -

Access DB performance issues My Access DB site is performing poorly on the clustered architecture. What are the possible reasons/solutions? For the most part MS Access databases suit web applications reasonably well; however, high traffic sites may benefit from upgrading to a true multi-user database platform such as MS SQL or perhaps even MySQL. We have found that sporadic performance issues occur when traffic intensive sites run on Microsoft Jet and IIS. We have ensured that our system is using the latest Microsoft Jet Components and Updates. We recommend that the native Jet OLE DB provider be used in place of the Access ODBC Driver. Excerpt from Readme.txt (IIS) For performance and reliability reasons, we strongly recommend the use of Microsoft SQL Server for the deployment of production-quality Web applications. Although Active Server Pages works with any ODBC-compliant database, it has been extensively tested and is designed to work with Microsoft SQL Server. ASP also supports Microsoft Access as a valid data source. Although the sample Web site and examples in this release use Microsoft Access, we recommend that Microsoft Access be used solely for development purposes and not for production. Microsoft Access was designed as a single-user desktop database, and not for server use. When multiple, concurrent users make requests of a Microsoft Access database, unpredictable results may occur. Please note that Microsoft has found the following line from the statement to be incorrect "Microsoft Access was designed as a single-user desktop database". The following article outlines Microsoft's recommendations to implement an SQL Server Database for use under IIS to accommodate for web, commerce, and transactional applications. http://support.microsoft.com/default.aspx?scid=kb;en-us;q299973 Created on 11/30 2005-25 -

Can I use Custom DLL s /Active X components? Custom DLL s/active X components are prohibited on the hybrid system. Components that are poorly coded tend to cause server instability, excessive resource consumption, and reduced site performance. Since we aim at offering the most stable, robust, and reliable clustered hosting environment, we unfortunately cannot take a chance of putting custom DLL s into production. Can I use Custom CFM tag s? Custom CFM tag s are prohibited on the hybrid system. Tags that are poorly coded tend to cause server instability, excessive resource consumption, and reduced site performance. Since we aim at offering the most stable, robust, and reliable clustered hosting environment, we unfortunately cannot take a chance of putting custom CFM tag s into production Supported Components / tags What Third-Party Components are currently installed? The following third-party COM components are currently installed: ASP Mail ASP JPEG ASP Upload ASP Encrypt SA-FileUP Jmail CDONTS Soapbox Toolkit 2.0 SP1 SmartMail SmartUpload (Other components may be installed at the discretion of the Hostplus.) Created on 11/30 2005-26 -

Payment Gateways Which Payment Gateways are installed on the Hybrid Platform? The following third-party Payment Gateways are currently installed: PayFlow Pro (replacement of Cybercash which is discontinued) Linkpoint PSI Gate (Other Payment Gateways may be installed at the discretion of the Hostplus.) SSL How are SSL considerations handled on the Hybrid? SSL for ASP or ColdFusion pages are managed identically to HTML pages on the hybrid. Each server in the Hybrid farm is configured to handle SSL connections from domains within our infrastructure. Please Note: To have a domain activated for ASP or ColdFusion SSL, please direct the end-user to the Windows Services in the WebSiteOS. Please note, this activation could take up to 24 hours to complete. Created on 11/30 2005-27 -

Supported Components/Tags Which Versions and Supported Components/tags do you support? Application Version/Supported Tech. Windows Services CGI Support FrontPage 2002 Extensions V.2002 Ms Access Database MS/MY SQL Database ASP V.3 on Win2000 (including: VBScript, JScript, MS XML4 SP2) and IIS6 on Windows 2003, ColdFusion PERLV.5.006.001 4.2.2 V.2002 and higher MS SQL =V.2000 MySQL=V.3.23.31 PHP ASP Mail 4.0 ASP JPEG 1.2 ASP UPLOAD 2.6 ASP Encrypt 2.1 CDONTS JMAIL SA-FileUP 3.5 Soapbox Toolkit 2.0 SP1 CGZIP SmatMail SmartUpload ASP Supported Components E-Commerce Gateways: PayFlowPro (replacement of Cybercash which is discontinued) PSI Gate Created on 11/30 2005-28 -

Supported ColdFusion Tags CFABORT CFMAIL CFAPPLET CFMAILPARAM CFAPPLICATION CFMODULE CFASSOCIATE CFOBJECT CFAUTHENTICATE CFOUTPUT CFBREAK CFPARAM CFCACHE CFPOP CFCOL CFPROCESSINGDIRECTIVE CFCOLLECTION CFPROCPARAM CFCOOKIE CFPROCRESULT CFDUMP CFQUERY CFERROR CFQUERYPARAM CFEXIT CFREPORT CFFILE CFRETHROW CFFLUSH CFSAVECONTENT CFFORM CFSCHEDULE CFGRAPH CFSCRIPT CFGRAPHDATA CFSEARCH CFGRID CFSELECT CFGRIDCOLUMN CFSERVLET CFGRIDROW CFSERVLETPARAM CFGRIDUPDATE CFSET CFHEADER CFSETTING CFHTMLHEAD CFSILENT CFHTTP CFSLIDER CFHTTPPARAM CFSTOREDPROC CFIF CFSWITCH CFELSEIF CFCASE CFELSE CFDEFAULTCASE Created on 11/30 2005-29 -

CFIMPERSONATE CFINCLUDE CFINDEX CFINPUT CFINSERT CFLDAP CFLOCATION CFLOCK CFLOOP CFTABLE CFTEXTINPUT CFTHROW CFTRANSACTION CFTREE CFTREEITEM CFTRY CFCATCH CFUPDATE CFWDDX Unsupported ColdFusion Tags CFCONTENT CFDIRECTORY CFREGISTRY CFADMINSECURITY CFEXECUTE CFFTP CFLOG Created on 11/30 2005-30 -

Coding Examples ASP (ASP) DSN connection for MS Access Solution: Set conn = Server.CreateObject("ADODB.Connection") conn.open "DSN=prefix_domain_com (ASP) DSN connection for MS SQL Solution: Set conn = Server.CreateObject("ADODB.Connection") conn.open "DSN= prefix_domain_com;uid=dbm.domain.com;pwd=password" (ASP) DSN connection for MySQL Solution: Set conn = Server.CreateObject("ADODB.Connection") conn.open "DSN= prefix_domain_com;uid=dbm.domain.com;pwd=password" (ASP) DSNless Connection for MS Access Set Conn = Server.CreateObject("ADODB.Connection") Conn.Open "PROVIDER=MICROSOFT.JET.OLEDB.4.0;DATA SOURCE=" & Server.MapPath( /databse.mdb ) mdbfile = "/stuff/sample.mdb" connstr = "Driver={Microsoft Access Driver (*.mdb);dbq=" & Server.MapPath( mdbfile ) & ";" Created on 11/30 2005-31 -

(ASP) DSNless connection for MS SQL DRIVER={SQL Server;SERVER=mssql.megasqlservers.com;DATABASE= databasename _domain_com;uid=dbm_domain_com;pwd=password; (ASP) DSNless connection for MySQL Driver={MySQL;Server=megasqlservers.com;DATABASE=databasen ame_domain_com;uid=dbm.domainname.com;pwd=password; (ASP) Defining Paths Server.MapPath("/") equates to \domain.com\public\ Server.MapPath("/images") equates to \domain.com\public\images Created on 11/30 2005-32 -

Coldfusion (Coldfusion) DSN connection for MS Access <cfquery name="schedule" datasource="db_domain _com"> SELECT * FROM Producers </cfquery> (Coldfusion) DSN connection for MS SQL <cfquery name="schedule" datasource="db_domain_com";server= mssql.megasqlservers.com ;UID= dbm.domain.com ;PWD= password > SELECT * FROM Producers </cfquery> Coldfusion) DSN connection for MySQL <cfquery name="schedule" datasource="db_domain_com"> SELECT * FROM Producers </cfquery> (Coldfusion) DSNless Connection for MS Access <CFSET thispath=expandpath("data\")> <CFSET thisdirectory= GetDirectoryFromPath("thisPath")> <CFQUERY NAME="test" DBTYPE="dynamic" CONNECTSTRING="Driver={Microsoft Access Driver (*.mdb);dbq=#getdirectoryfrompath(thispath)#mydb.mdb;"> SELECT * FROM MyTable </CFQUERY> Created on 11/30 2005-33 -

(Coldfusion) DSNless connection for MS SQL <CFQUERY NAME="test" DBTYPE="dynamic" CONNECTSTRING=" Driver={SQL Server;Server=servername;Database=dbname;Uid=sa;Pwd=pass;" > SELECT * FROM MyTable </CFQUERY> (Coldfusion) DSNless connection for MySQL <CFQUERY NAME="test" DBTYPE="dynamic" CONNECTSTRING=" Driver={mysql;Server=servername;Database=dbname;Uid=sa;Pwd =pass;"> SELECT * FROM MyTable </CFQUERY> (Coldfusion) Defining Paths <CFSET thispath= ExpandPath("images/")> <CFSET thisdirectory= GetDirectoryFromPath(thisPath)> This equates to the following path: \domain.com\public\images Created on 11/30 2005-34 -

ASP.NET (ASP.NET) DSN connection for MS Access <%@ import Namespace="System.Data" %> <%@ import Namespace="System.Data.Odbc" %> <%@ Page Language="C#" %> <script runat="server"> public void Page_Load(Object sender, EventArgs e) { DataTable dtrecords = GetDataTable("SELECT * FROM info"); foreach(datarow dr in dtrecords.rows) { Response.Write(dr["Name"].ToString() + " " + dr["phone"].tostring() + "<br/>"); private static string GetConnection() { return "DSN=db1_yourdomain_com"; public static DataTable GetDataTable(string sql) { DataTable rt = new DataTable(); DataSet ds = new DataSet(); OdbcDataAdapter da = new OdbcDataAdapter(); OdbcConnection con = new OdbcConnection(GetConnection()); OdbcCommand cmd = new OdbcCommand(sql, con); da.selectcommand = cmd; da.fill(ds); try { rt = ds.tables[0]; catch { rt = null; return rt; </script> Created on 11/30 2005-35 -

(ASP.NET) DSN connection for MS SQL <%@ import Namespace="System.Data" %> <%@ import Namespace="System.Data.Odbc" %> <%@ Page Language="C#" %> <script runat="server"> public void Page_Load(Object sender, EventArgs e) { DataTable dtrecords = GetDataTable("SELECT * FROM table1"); foreach(datarow dr in dtrecords.rows) { Response.Write(dr["name"].ToString() + " " + dr["lname"].tostring() + "<br/>"); private static string GetConnection() { return "DSN=db2_yourdomain_com;UID=dbm.youdomain.com;PWD=passwor d"; public static DataTable GetDataTable(string sql) { DataTable rt = new DataTable(); DataSet ds = new DataSet(); OdbcDataAdapter da = new OdbcDataAdapter(); OdbcConnection con = new OdbcConnection(GetConnection()); OdbcCommand cmd = new OdbcCommand(sql, con); da.selectcommand = cmd; da.fill(ds); try { rt = ds.tables[0]; catch { rt = null; return rt; </script> Created on 11/30 2005-36 -

(ASP.NET) DSN connection for MySQL <%@ import Namespace="System.Data" %> <%@ import Namespace="System.Data.Odbc" %> <%@ Page Language="C#" %> <script runat="server"> public void Page_Load(Object sender, EventArgs e) { DataTable dtrecords = GetDataTable("SELECT * FROM table1"); foreach(datarow dr in dtrecords.rows) { Response.Write(dr["name"].ToString() + " " + dr["lname"].tostring() + "<br/>"); private static string GetConnection() { return "DSN=db_domain_com;UID=dbm.domain.com;password=pass"; public static DataTable GetDataTable(string sql) { DataTable rt = new DataTable(); DataSet ds = new DataSet(); OdbcDataAdapter da = new OdbcDataAdapter(); OdbcConnection con = new OdbcConnection(GetConnection()); OdbcCommand cmd = new OdbcCommand(sql, con); da.selectcommand = cmd; da.fill(ds); try { rt = ds.tables[0]; catch { rt = null; return rt; </script> Created on 11/30 2005-37 -

(ASP.NET) DSNless Connection for MS Access <%@ Import Namespace="System.Data.OleDb" %> <script runat="server"> sub Page_Load dim dbconn,sql,dbcomm,dbread dbconn=new OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;data source=" & server.mappath("db/aspx.mdb")) Created on 11/30 2005-38 -

(ASP.NET) DSNless connection for MS SQL <%@ import Namespace="System.Data" %> <%@ import Namespace="System.Data.Odbc" %> <%@ Page Language="C#" %> <script runat="server"> public void Page_Load(Object sender, EventArgs e) { DataTable dtrecords = GetDataTable("SELECT * FROM table1"); foreach(datarow dr in dtrecords.rows) { Response.Write(dr["name"].ToString() + " " + dr["lname"].tostring() + "<br/>"); private static string GetConnection() { return "DRIVER={SQL Server;Server=mssql.megasqlservers.com;Database=db_yourd omain_com;uid=dbm.yourdomain.com;pwd=password"; public static DataTable GetDataTable(string sql) { DataTable rt = new DataTable(); DataSet ds = new DataSet(); OdbcDataAdapter da = new OdbcDataAdapter(); OdbcConnection con = new OdbcConnection(GetConnection()); OdbcCommand cmd = new OdbcCommand(sql, con); da.selectcommand = cmd; da.fill(ds); try { rt = ds.tables[0]; catch { rt = null; return rt; </script> Created on 11/30 2005-39 -

(ASP.NET) DSNless connection for MySQL <%@ import Namespace="System.Data" %> <%@ import Namespace="System.Data.Odbc" %> <%@ Page Language="C#" %> <script runat="server"> public void Page_Load(Object sender, EventArgs e) { DataTable dtrecords = GetDataTable("SELECT * FROM table1"); foreach(datarow dr in dtrecords.rows) { Response.Write(dr["name"].ToString() + " " + dr["lname"].tostring() + "<br/>"); private static string GetConnection() { return "DRIVER={MySQL ODBC 3.51 Driver;Server=sql.megasqlservers.com;Database=db_yourdom ain_com;uid=dbm.yourdomain.com;password=password"; public static DataTable GetDataTable(string sql) { DataTable rt = new DataTable(); DataSet ds = new DataSet(); OdbcDataAdapter da = new OdbcDataAdapter(); OdbcConnection con = new OdbcConnection(GetConnection()); OdbcCommand cmd = new OdbcCommand(sql, con); da.selectcommand = cmd; da.fill(ds); try { rt = ds.tables[0]; catch { rt = null; return rt; </script> Created on 11/30 2005-40 -