Search results for query: *

Here's something - Make sure the NAME of the SERVER under cfadministrator is the SAME NAME as the name you used in the client configuration option when you set up a manual ODBC connection. Chances are it's a name resolution issue Also, try this Under the Sql Server Programs Menu in Start...

If you're using IIS, you can also do this: Under properties for the site, click the http-headers Tab click enable content expiration Click expire content immediately Also, in your cfadministrator, under caching make sure the "use trusted cache" checkbox is not checked. Hope this...

I have applied sp3 to over 5 machines running cf 5 and/or mx. There are absolutely no problems I've run into. You better do it ASAP though because there is a virus out there that attacks SQL servers w/sp3.

Screw setting up a DNS server and use one of the free one's- mydomain.com is good.

I addressed this in another forum as well - it's all here: http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q320700&

I had the same problem running Win2000 Server and found an a tech note on the MS website about it. Apparently it's a result of the MDAC's OLEDB (v2.5-2.7) doing it. I believe there's a fix in the latest SQL service packs, but here's the technote and like to the hotfix...