Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Erland Sommarskog Newsgroups: comp.databases.ms-sqlserver Subject: Re: Odbc and client library/drivers Date: Tue, 18 Sep 2012 21:57:15 +0200 Organization: Erland Sommarskog Lines: 27 Message-ID: References: <94298aed-7cbb-41f8-a155-c4632fc9db35@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Injection-Info: mx04.eternal-september.org; posting-host="9c1143bfab35549403b85d70ea1a57d8"; logging-data="28047"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18802oF4yQQ6cq9DgWzQejM" User-Agent: Xnews/2006.08.24 Mime-proxy/2.1.c.0 (Win32) Cancel-Lock: sha1:ndcdKK5PT7nkMey4yd67mphiazs= Xref: csiph.com comp.databases.ms-sqlserver:1293 björn lundin (b.f.lundin@gmail.com) writes: > That comes up time after time. > If we > > select * from sometable > > And retrive the colunms in another order than the selcect presents them, > we get a failure. I know this is the client lib 'optimising' by dropping > data it does think i do not want. > > I wonder if there exists such an odbc client lib other than the one that > get installed on the server, That allows me to retrive values from a > resultset in the column order i like? You should use SQL Server Native Client 10 as the ODBC driver if you are on SQL 2008, not SQL Server, which is an old driver. Whether this resolves the issue you are talking about I don't know. But you should not use SELECT * in production code. -- Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx