The include file that applyConnection() generates declares all the properties of a connection. The filename for the include file is the connection name. It has the filename extension that is defined for the server model associated with the current site.
Connections are shared, so set the allowMultiple value to false. It ensures that the connection file is included in the document only once. It also ensures that the server script remains in the page if any other server behaviors use it.
You can see some sample include files that applyConnection() generates for various default server models illustrated in the coming sections.
To create a connection include file format, define a new EDML mapping file, which is like connection_includefile.edml, as shown in The definition file for your connection type.
<% // Filename="Connection_ado_conn_string.htm" // Type="ADO" // HTTP="true" // Catalog="" // Schema="" var MM_MyConnection1_STRING = "dsn=pubs"; %>
The server behavior file includes this connection by using the relative file include statement, as shown in the following example:
When you use UltraDev 4 ColdFusion, Dreamweaver relies on a ColdFusion include file to get a list of data sources.
For regular Dreamweaver ColdFusion, Dreamweaver ignores any include files and, instead, makes use of RDS to retrieve the list of data sources from ColdFusion.
The UltraDev 4 ColdFusion include file should be named MyConnection1.cfm, where MyConnection1 is the name of your connection. The following example shows the include file for a ColdFusion connection to a product table:
<!-- FileName="Connection_cf_dsn.htm" "dsn=products" --> <!-- Type="ADO" --> <!-- Catalog="" --> <!-- Schema="" --> <!-- HTTP="false" --> <CFSET MM_MyConnection1_DSN = "products"> <CFSET MM_MyConnection1_USERNAME = ""> <CFSET MM_Product_USERNAME = ""> <CFSET MM_MyConnection1_PASSWORD = "">
The server behavior file includes this connection by using the cfinclude statement, as shown in the following example: