Thanks, turns out the problem machine did not have
all the Service Packs up-to-date. Fixed now.

On Mon, 17 Nov 2003 14:39:32 GMT, "Jerry Boone"
<jerry@antech.biz.nospam> wrote:

>Bruce,
>
>I feel your pain. I know exactly what your are talking about but can't
>remember what I did that broke and fixed it for sure.
>
>Hmm, this may be a long shot, but you might want to run "cliconfg" and see
>if your using the same default protocol on the client as it is on your dev
>unit. Using Named Pipes might be what is causing it. If it is, you can
>actually go into the Server Network Utility on the SQL Server and set your
>default protocol to TCP/IP and your clients will follow that.
>
>Also, I use integrated/domain security so I can deploy generic ADE's to my
>users. Then, when they open, their windows credentials are used to auth
>with Sql.