Re: Problems with SQLEXEC
- From: tg <tganss_at_t_dash_online_dot_de-remove-all-after-first-real-dash@xxxxxxxxx>
- Date: Thu, 29 May 2008 16:31:36 +0200
Hi Olaf,
I think this goes wrong, if the used driver is "SQL Native Client"
instead of "SQL Server". Another problem with the Native Client
driver was Varchar(MAX) sometimes retrieved as C(0) (depending
on the first row of the resultset). SQL Native Client seems to
"optimize" the resultset or VFP has it's usual way of determining
the record structure.
Was the schema-property set and CA configured to use the schema ?
My first thought would be to enforce the resulting cursorschema this way.
I think with "Driver=SQL Server" in the connection string everything
is fine including the Varchar(Max) problem. I try to reproduce those
errors.
thanks
thomas
.
- References:
- Problems with SQLEXEC
- From: Somnath Gupta
- Re: Problems with SQLEXEC
- From: Dan Freeman
- Re: Problems with SQLEXEC
- From: somnat
- Re: Problems with SQLEXEC
- From: Dan Freeman
- Re: Problems with SQLEXEC
- From: somnat
- Re: Problems with SQLEXEC
- From: Olaf Doschke
- Re: Problems with SQLEXEC
- From: tg
- Problems with SQLEXEC
- Prev by Date: Re: Unique Identification Numbering
- Next by Date: MSCAL.OCX v7 overwritten by v11 of control?
- Previous by thread: Re: Problems with SQLEXEC
- Next by thread: Re: Problems with SQLEXEC
- Index(es):
Relevant Pages
|