I agree with you on using servername and port. I've never been able to
get SQL Server connected in any CF engine (ACF, OpenBD, Railo) or any
driver (including jTDS and Microsoft) using servername\instancename.
Carl
On 7/6/2011 11:40 AM, Matthew Woodward wrote:
On Wed, Jul 6, 2011 at 11:24 AM, Carl Von Stetten
<[email protected] <mailto:[email protected]>> wrote:
If 1433 is the correct port, try dropping the instance name off in
BD Admin (just use WIN-3QK2B4MSNH5). And just for reference,
SQLEXPRESS is not a default instance name but a named instance.
It's just the default option when installing SQL Server Express
Edition (you can specify that it use a default instance instead).
Thanks--great into to have. Even when our DBAs set up named instances
on SQL Server I always just use the server name and port number so
good point to start there and see how it goes.
I'm still thinking this has to be a behavior change with the newer
drivers but hopefully with some additional troubleshooting we can get
to the bottom of it.
--
Matthew Woodward
[email protected] <mailto:[email protected]>
http://blog.mattwoodward.com
identi.ca <http://identi.ca> / Twitter: @mpwoodward
Please do not send me proprietary file formats such as Word,
PowerPoint, etc. as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html
--
official tag/function reference: http://openbd.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
--
official tag/function reference: http://openbd.org/manual/
mailing list - http://groups.google.com/group/openbd?hl=en
