Hi,
I have an Oracle 8.1.7 server and I'm extracting a Varchar2(length 300)
using an aspx page and the field is always Null, even if it's not in the DB.
I tried the EXACT same code in a windows form and it works perfect.

Is there a bug in asp.net/ado.net with Varchar2 bigger than 256 char ? (I
have no problems with Varchar2 of length < 256).

Also, I tried creating a copy of my table with a Varchar1 instead of the
Varchar2 and it worked too (>256).

Found my problem to be related to oracle tablespace being corrupted...

"plumeprog" wrote:

> Hi,
> I have an Oracle 8.1.7 server and I'm extracting a Varchar2(length 300)
> using an aspx page and the field is always Null, even if it's not in the DB.
> I tried the EXACT same code in a windows form and it works perfect.
>
> Is there a bug in asp.net/ado.net with Varchar2 bigger than 256 char ? (I
> have no problems with Varchar2 of length < 256).
>
> Also, I tried creating a copy of my table with a Varchar1 instead of the
> Varchar2 and it worked too (>256).

Auch, can you elaborate?

I have not seen this problem before and it would be interesting to know how
the tablespace was corrupted and how you found out.
Thank you,

--
Angel Saenz-Badillos [MS] Managed Providers
This posting is provided "AS IS", with no warranties, and confers no
rights.Please do not send email directly to this alias.
This alias is for newsgroup purposes only.
I am now blogging about ADO.NET: http://weblogs.asp.net/angelsb/




"plumeprog" <(E-Mail Removed)> wrote in message
news:3F26C113-61B1-46E4-9FBC-(E-Mail Removed)...
> Found my problem to be related to oracle tablespace being corrupted...
>
> "plumeprog" wrote:
>
> > Hi,
> > I have an Oracle 8.1.7 server and I'm extracting a Varchar2(length 300)
> > using an aspx page and the field is always Null, even if it's not in the
DB.
> > I tried the EXACT same code in a windows form and it works perfect.
> >
> > Is there a bug in asp.net/ado.net with Varchar2 bigger than 256 char ?
(I
> > have no problems with Varchar2 of length < 256).
> >
> > Also, I tried creating a copy of my table with a Varchar1 instead of the
> > Varchar2 and it worked too (>256).