Re: SQL Server + ADO = empty fields
From: Aaron [SQL Server MVP] (ten.xoc_at_dnartreb.noraa)
Date: 06/02/04
- Next message: Andrew J. Kelly: "Re: Create Job to Delete Transaction Log Once a Week"
- Previous message: rc: "SQL Server + ADO = empty fields"
- In reply to: rc: "SQL Server + ADO = empty fields"
- Next in thread: rc: "Re: SQL Server + ADO = empty fields"
- Reply: rc: "Re: SQL Server + ADO = empty fields"
- Reply: rc: "Re: SQL Server + ADO = empty fields"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 2 Jun 2004 09:43:42 -0400
Could you consider showing us the DDL for the table, some sample data, the
stored procedure, and the VB code that causes the issue?
http://www.aspfaq.com/5006
-- http://www.aspfaq.com/ (Reverse address to reply.) "rc" <no@email.com> wrote in message news:#Qp73cKSEHA.2520@TK2MSFTNGP11.phx.gbl... > Hello, > > > > Back end - SQL Server 2000 > > Front end - Access 2000 > > > > > > I have a basic table with about 20 columns. I retrieve data via a stored > procedure. If I run the stored procedure (the select statement) in Query > Analyzer, the data returned is exactly what I requested. > > > > In Access, I'm using unbound forms and connecting to SQL Server via ADO. If > I try to fill a recordset with the same stored procedure, some fields come > back as "empty". > > > > For example, I have one column with a bit data type (1 or 0). I know that > each row contains a "1" in the column. However, debugging the VB code in > access, I find that these columns are returning as "empty" (I've confirmed > this by coding an "if isempty()" function into the code that fills the > recordset). > > > > Now, the strange thing, if I rearrange the order of columns via the "Design > Table" in SQL Server (e.g. Moving the column to the top), everything works > fine. The recordset is filled with correct data. > > > > This work a round does seem to work, but is this really necessary? > > > > Anyone know why this happens?? > > > > > > Any insight would be helpful. > > > > > > Thank You > >
- Next message: Andrew J. Kelly: "Re: Create Job to Delete Transaction Log Once a Week"
- Previous message: rc: "SQL Server + ADO = empty fields"
- In reply to: rc: "SQL Server + ADO = empty fields"
- Next in thread: rc: "Re: SQL Server + ADO = empty fields"
- Reply: rc: "Re: SQL Server + ADO = empty fields"
- Reply: rc: "Re: SQL Server + ADO = empty fields"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|