RE: SQL Server on a separate machine

2002-02-12 Thread Bill Grover
> To: CF-Talk > Subject: RE: SQL Server on a separate machine > > > Dave, > > Well ok, so you're right (dang it). I missed the word > "admin" > skipped right over it in good faith . sorry. And I agree > with you - bad > Idea. > >

RE: SQL Server on a separate machine

2002-02-11 Thread Bill Grover
W:http://www.euservices.com __ > -Original Message- > From: Kay Smoljak [mailto:[EMAIL PROTECTED]] > Sent: Sunday, February 10, 2002 9:04 PM > To: CF-Talk > Subject: RE: SQL Server on a separate machine > > > > OK. At

RE: SQL Server on a separate machine

2002-02-10 Thread Kay Smoljak
> OK. At this point, I'd try the MDAC upgrade, personally. I just installed 2.7, and I'm still getting exactly the same error message. > You should be able to connect with an SQL login - a username > and password created within the SQL Enterprise Manager. That > would be the ideal solution. If

RE: SQL Server on a separate machine

2002-02-10 Thread Dave Watts
> > Maybe it's an MDAC problem. You might download and install > > the latest MDAC, which is 2.7, from http://www.microsoft.com/mdac/. > > > Or, maybe you're not specifying the other information in the > > CF Administrator properly, though that seems unlikely. You > > might try writing a page

RE: SQL Server on a separate machine

2002-02-10 Thread Kay Smoljak
> Maybe it's an MDAC problem. You might download and install > the latest MDAC, which is 2.7, from http://www.microsoft.com/mdac/. > Or, maybe you're not specifying the other information in the > CF Administrator properly, though that seems unlikely. You > might try writing a page with a CFQUE

RE: SQL Server on a separate machine

2002-02-10 Thread Andy Parry
n CF Admin may solve the problem. HTH andy > -Original Message- > From: Kay Smoljak [mailto:[EMAIL PROTECTED]] > Sent: Monday, 11 February 2002 8:58 AM > To: CF-Talk > Subject: Re: SQL Server on a separate machine > > > Thanks for your help. > > I have chan

Re: SQL Server on a separate machine

2002-02-10 Thread Daniel Quinones
AIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Sunday, February 10, 2002 7:58 PM Subject: Re: SQL Server on a separate machine > Thanks for your help. > > I have changed the SQL Server security tab settings on the server to > allow "SQL Server &

RE: SQL Server on a separate machine

2002-02-10 Thread Dave Watts
> I have changed the SQL Server security tab settings on the > server to allow "SQL Server & Windows" authentication. I have > set the DSN up on my local machine using Windows ODBC and it > verifies fine. I then look it up in the CF administrator and > it fails. I have tried: > > - Named pipe

Re: SQL Server on a separate machine

2002-02-10 Thread Marlon Moyer
From: "Kay Smoljak" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Sunday, February 10, 2002 6:58 PM Subject: Re: SQL Server on a separate machine > Thanks for your help. > > I have changed the SQL Server security tab settings on the server to

Re: SQL Server on a separate machine

2002-02-10 Thread Kay Smoljak
Thanks for your help. I have changed the SQL Server security tab settings on the server to allow "SQL Server & Windows" authentication. I have set the DSN up on my local machine using Windows ODBC and it verifies fine. I then look it up in the CF administrator and it fails. I have tried: - Named

Re: SQL Server on a separate machine

2002-02-07 Thread Bryan Stevenson
set username and password for the datasource in CF Admin Bryan Stevenson VP & Director of E-Commerce Development Electric Edge Systems Group Inc. p. 250.920.8830 e. [EMAIL PROTECTED] - Macromedia Associate Partner www.macromedia.com

RE: SQL Server on a separate machine

2002-02-06 Thread Andy Parry
Hi kay, one other thing, if you want to configure your SQL server for trusted connections or otherwise, go to Enterprise Manager, select Properties of the server and click on Security tab. Select either Windows (for trusted) or SQLServer+Windows (for either) as your connection type. HTH andy

RE: SQL Server on a separate machine

2002-02-06 Thread Andy Parry
Hi Kay, Check your ODBC configuration on your client machine, as it might be that, rather than the SQL Server config. The SQL Server ODBC driver may be configured to use "With Windows Authentication" and you can change this to "With SQL Server authentication" Alternatively, if you do need to use T