"Syntax error or access violation" with new (July 22 2003) driver

Hi,
I'm having troubles with the SQL Server ODBC driver 2000.81.9001.40 dated on
July 22 2003. It is incompatible with our custom application developed with
Centura SQLWindows/32 Version 1.5.1-PFT2. When running some queries, the
error message reported by the driver is
Error No: 20035
Error Text: [Microsoft][ODBC SQL Server Driver]Syntax error or access
violation
The only suspicious fact is that the command is broken by a CR-LF (new line)
combination. This code had worked for years without any problem, sending
such broken line commands
The SQL command sent is:
{call spEjeSelectRem ('vCtePedTem_ChecaPoliticas
20,20,159,1,935502,17700024,1200148,null,
1')}
Note there is a new-line sequence behind the last parameter
My questions are:
Can It be the cause of the above mentioned error?
Wat can I do, install the previous version?
The ODBC driver is dated July 22 2003. It was automatically downloaded by
Microsoft Automatic Update. How can I protect specifically from ODBC driver
version updates?
Thanks in advance
FaustinoOk,
I did the following:
-"Uninstall" MDAC by
dasetup.exe /u
(actually the uninstall procedure didn't work, but at least it leave the
ODBC in such inconsistent state that I could install a previous version)
-Installed the MDAC v.2.7 that I had before the bug appeared. The bug didn't
appear again.
However yesterday the Microsoft Update suggested to install the security
patch 823718 related to MDAC. I crossed my fingers and applied it. No
problem. SQL Server driver is now 2000.81.9041.40 and the bug didn't show
again.
Hope this helps somebody
Faustino
"faustino Dina" <fdina@.matusa.com.mx> wrote in message
news:eo%23$lJ%23aDHA.2016@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I'm having troubles with the SQL Server ODBC driver 2000.81.9001.40 dated
on
> July 22 2003. It is incompatible with our custom application developed
with
> Centura SQLWindows/32 Version 1.5.1-PFT2. When running some queries, the
> error message reported by the driver is
> Error No: 20035
> Error Text: [Microsoft][ODBC SQL Server Driver]Syntax error or access
> violation
> The only suspicious fact is that the command is broken by a CR-LF (new
line)
> combination. This code had worked for years without any problem, sending
> such broken line commands
> The SQL command sent is:
> {call spEjeSelectRem ('vCtePedTem_ChecaPoliticas
> 20,20,159,1,935502,17700024,1200148,null,
> 1')}
> Note there is a new-line sequence behind the last parameter
> My questions are:
> Can It be the cause of the above mentioned error?
> Wat can I do, install the previous version?
> The ODBC driver is dated July 22 2003. It was automatically downloaded by
> Microsoft Automatic Update. How can I protect specifically from ODBC
driver
> version updates?
> Thanks in advance
> Faustino
>

"Custom" Report Model Data Source?

Hello,
Is this a true statement: "The only Data Sources available to a Report Model
are SQL Server 2000, SQL Server 2005, and SQL Server Analysis Services 2005"?
I had read somewhere that there was going to be an ability to specify a
"custom" query processors so that you could use data sources in addition to
the items listed above.
Thanks!I don't think so...
Since you can use ADO.Net every supported DataRpovider should work with
it... at least in local reports
"brianpmccullough" <bmccullough11@.comcast.net> wrote in message
news:2A5B524A-176B-4BD2-ACC2-75C9C3DDB2DA@.microsoft.com...
> Hello,
> Is this a true statement: "The only Data Sources available to a Report
> Model
> are SQL Server 2000, SQL Server 2005, and SQL Server Analysis Services
> 2005"?
> I had read somewhere that there was going to be an ability to specify a
> "custom" query processors so that you could use data sources in addition
> to
> the items listed above.
> Thanks!
>

"Custom Reports..." grayed out, SP2 (latest) installed

What am I missing, here? The "Custom Reports..." context menu appears, but
is grayed out, and no "Standard Reports" context menu item is there. I've
found no reference to additional steps to get these reports enabled/visible.
Help?
thanks,Where exactly you see all these things ?
Amarnath
"Stan Spotts [Computer Aid, Inc]" wrote:
> What am I missing, here? The "Custom Reports..." context menu appears, but
> is grayed out, and no "Standard Reports" context menu item is there. I've
> found no reference to additional steps to get these reports enabled/visible.
> Help?
> thanks,|||In SQL Server Management Studio.
"Amarnath" wrote:
> Where exactly you see all these things ?
> Amarnath
> "Stan Spotts [Computer Aid, Inc]" wrote:
> > What am I missing, here? The "Custom Reports..." context menu appears, but
> > is grayed out, and no "Standard Reports" context menu item is there. I've
> > found no reference to additional steps to get these reports enabled/visible.
> >
> > Help?
> >
> > thanks,

"CREATE TABLE" for files *.dbf with a custom float column

How to create dbase file based on SQL-92 which have a FLOAT column like
float(14,2):
=> xxxxxxxxxxxxxx,xx <=
Thanks in advance,
PatriceN(14,2)
"news.microsoft.com" <reprotechnic@.wanadoo.fr> escribi en el mensaje
news:u37grkt#DHA.2072@.TK2MSFTNGP11.phx.gbl...
> How to create dbase file based on SQL-92 which have a FLOAT column like
> float(14,2):
> => xxxxxxxxxxxxxx,xx <=
> Thanks in advance,
> Patrice
>|||this solution doesn't run. it makes a float column of (20,4).
With more precision, i test this with odbc.net from Framework.NET v1.1
"Luis Camacho" <luibrac@.yahoo.com.ar> a crit dans le message de
news:%23VMvv5K$DHA.1036@.TK2MSFTNGP10.phx.gbl...
> N(14,2)
> "news.microsoft.com" <reprotechnic@.wanadoo.fr> escribi en el mensaje
> news:u37grkt#DHA.2072@.TK2MSFTNGP11.phx.gbl...
>|||N(14,2): This does not work and gives a syntax error on command.
AndreB.
"Luis Camacho" <luibrac@.yahoo.com.ar> a crit dans le message de
news:%23VMvv5K$DHA.1036@.TK2MSFTNGP10.phx.gbl...
> N(14,2)
> "news.microsoft.com" <reprotechnic@.wanadoo.fr> escribi en el mensaje
> news:u37grkt#DHA.2072@.TK2MSFTNGP11.phx.gbl...
>

"...remote name could not be resolved" when using custom Web App

Hi all,
I'm getting a headache trying to figure out what is going on here. I've set
up Reporting Services on 1 dev machine and 2 servers and using a Web
Application that I am developing to access Reporting Services to generate a
report for me. Everything works fine on both my development machine and one
of the servers, but the other server keeps on producing this error:
"The underlying connection was closed: The remote name could not be resolved."
As far as I can remember, every instance of RS was installed identically.
Also, I can use the Report Manager from the server and from networked
computers to generate reports with no issues. Its only upon my Web Apps
access to the RS that I get this error. Is this similar to the SSL issues a
lot of people have been discussing? I'm still quite a newbie when it comes to
sql server and iis, so if this has been answered elsewhere already, I'd
appreciate a link :)
AndreAfter a bit of debugging I found that the problem was actually just that a
static web refference to the report server was being used, and that was
pointing at the other server still.
All works fine now.