On Fri, Apr 4, 2008 at 4:00 PM, Jeff Johnson <[EMAIL PROTECTED]> wrote:
> FYI:
>
> http://blogs.msdn.com/sqlnativeclient/archive/2006/09/27/774282.aspx
>
> Here is a snippet from there :
>
> Must I upgrade clients to use SQL Native Client as soon as I upgrade my
> server?
>
--
On Fri, Apr 4, 2008 at 3:26 PM, kam <[EMAIL PROTECTED]> wrote:
> I am in the process of converting to PostgreSQL. I would like to do
> everything I need using my existing DBC/DBF files first to be
> sure I have all the data access separated from the user interface and also
> get some experience. T
FYI:
http://blogs.msdn.com/sqlnativeclient/archive/2006/09/27/774282.aspx
Here is a snippet from there :
Must I upgrade clients to use SQL Native Client as soon as I upgrade my
server?
Applications deployed before SQL Server 2005 was released can and should
continue to use MDAC.
Applications
Endif
Endfor
loRS.MoveNext()
Enddo
Endif
- Original Message -
From: "Stephen Russell" <[EMAIL PROTECTED]>
To: "ProFox Email List"
Sent: Friday, April 04, 2008 12:55 PM
Subject: Re: SQL Passthrough and ODBC
On Fri, Apr 4, 2008 at 2:48 PM, kam <
On Fri, Apr 4, 2008 at 2:48 PM, kam <[EMAIL PROTECTED]> wrote:
> Can you show me the code to browse a specific table (or select * from
> MyTable)
>
> OConn is an object with properties so the code below seems to work. In
> this dbc there is a table named m6nmpt.dbf and a view to
> look at all the
Connection")
OConn.ConnectionString = "provider=vfpoledb.1;data
source=U:\ssi\304901\Share\ptshare.dbc"
OConn.Open
- Original Message -
From: "Stephen Russell" <[EMAIL PROTECTED]>
To: "ProFox Email List"
Sent: Friday, April 04, 2008 6:49 AM
Subject: Re
Jeff Johnson wrote:
> Thanks Ted & Steve: I use connectionstrings.com but I needed to know if
> sqlstringconnect, etc. uses ODBC. Connectionstrings.com clearly shows
> that my connections use ODBC and I have informed my customer.
SQLSTRINGCONNECT *does use* an ODBC driver, but *doesn't need to
Thanks Ted & Steve: I use connectionstrings.com but I needed to know if
sqlstringconnect, etc. uses ODBC. Connectionstrings.com clearly shows
that my connections use ODBC and I have informed my customer.
Jeff
Jeff Johnson
[EMAIL PROTECTED]
SanDC, Inc.
623-582-0323
Fax 623-869-0675
Stephen Ru
On Thu, Apr 3, 2008 at 4:49 PM, Jeff Johnson <[EMAIL PROTECTED]> wrote:
> I just received a question from a dba and I think I know the answer, but
> I really need to make sure. I am accessing MSSQL Server tables using
> SQL passthrough in VFP. I use SQLSTRINGCONNECT() and then send a select
> st
Jeff Johnson wrote:
> So where is says "driver={SQL Server}" that is an ODBC driver?
>
Yes. If you want to use the SQL Native Client driver instead it would be
along these lines;
Description=sql native client test;DRIVER=SQL Native
Client;SERVER=(local);Trusted_Connection=Yes;APP=Microsoft Vi
On Thu, Apr 3, 2008 at 6:55 PM, Jeff Johnson <[EMAIL PROTECTED]> wrote:
> So where is says "driver={SQL Server}" that is an ODBC driver?
Yeah, I'm pretty sure that's it.
--
Ted Roche
Ted Roche & Associates, LLC
http://www.tedroche.com
___
Post Messa
So where is says "driver={SQL Server}" that is an ODBC driver?
Jeff
Jeff Johnson
[EMAIL PROTECTED]
SanDC, Inc.
623-582-0323
Fax 623-869-0675
Ted Roche wrote:
> Read your SQLStringConnect. It ought to specify the SQL Server ODBC driver.
>
> On Thu, Apr 3, 2008 at 5:49 PM, Jeff Johnson <[EMAIL P
Read your SQLStringConnect. It ought to specify the SQL Server ODBC driver.
On Thu, Apr 3, 2008 at 5:49 PM, Jeff Johnson <[EMAIL PROTECTED]> wrote:
> I just received a question from a dba and I think I know the answer, but
> I really need to make sure. I am accessing MSSQL Server tables using
>
I just received a question from a dba and I think I know the answer, but
I really need to make sure. I am accessing MSSQL Server tables using
SQL passthrough in VFP. I use SQLSTRINGCONNECT() and then send a select
statement with SQLEXEC. They are moving from SQL2000 to SQL2005 and
wanted to
14 matches
Mail list logo
