Creating a datasource against sql 2005 express on fly for coldfusion8

Per another thread and based on Andy Allan's pointer and Nasir Ghaznavi's additional input, creating a datasource against a sql 2000 db was successful (did that a while ago), however, I think the Macromedia's JDBC does not support connection to a sql 2005 express database, for I've tried both manual and automatic ds setup to no avail.  But Microsoft's sql server 2005 JDBC driver would work.  Now the problem is, after looking at the cfadminapi's datasource.cfc documentation, I don't see any argument for a JDBC URL, e.g. jdbc:sqlserver://{serverName}\{instanceName}:{portNumber}... Any way to get it to work or a viable alternative for creating ds for such db platform on the fly? TIA.

> Per another thread and based on Andy Allan's pointer and Nasir Ghaznavi's additional > input, creating a datasource against a sql 2000 db was successful (did that a while ago), > however, I think the Macromedia's JDBC does not support connection to a sql 2005 > express database, for I've tried both manual and automatic ds setup to no avail. The SQL Server driver that comes with CF can connect to any version of SQL Server 2005 including Express. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information!

----- Excess quoted text cut - see Original Post for more ----- Thanks, Dave, but it's a bit odd.  Previously I've tried to use the MS SQL Server driver that comes with cf8 to no avail, but just now, it works, I think I used same setting/parameters, maybe I wasn't careful enough, possible.  Now, a problem, when referencing a sql server 2005's instance, one has to use the exact machine name but not (local) nor (localhost), but I need to use a generic one -- OS = XP w/ SP3. Tring to find the computer's name may likely be blocked for security reason. Further thought?

You can use the IP address, if that's an available option for you.  Even 127.0.0.1, if you're (horrors) running MSSQL and CF on the same box. ----- Excess quoted text cut - see Original Post for more -----

> You can use the IP address, if that's an available option for you.   > Even 127.0.0.1, if you're (horrors) running MSSQL and CF on the same > box. > Beautiful, thanks.  Previously I also tried it to no avail, maybe then my network security/firewall/anti-virus program setup etc. messed it up.

----- Excess quoted text cut - see Original Post for more ----- Cool, glad that worked.  Also be careful of named instances, if you have any servers with more than one MSSQL instance on them: IP won't be sufficient in those cases since you'll also need the instance name (127.0.0.1\instance-name or whatever).