Pesky DataColumn

  • Thread starter Thread starter scorpion53061
  • Start date Start date
S

scorpion53061

In this statement:

select CONVERT (CHAR(10), DATE, 101) AS DATEOFORDER

the dataset had it appear as "DATE" which was empty and as DATEOFORDER which
was as it should be.

If I try:
Dstran1.Tables(0).Columns.Remove("DATE")

it balks and says there is no column called "DATE"

I dont want to have an empty column so how should I get rid of it?
 
Hi scorp,

There should be on Dateoforder column in dataset so it is right that there
is no Date column.
Can you show some code or explain the problem a bit more?
 
Hi Miha,

The problem was resolved by using removeat....

but the original issue was that the "DATE" column was appearing as an empty
field in the report and DATEOFORDER was appearing as well.

I think it has to do with how the dataset is built not the SQL statement.

I might be wrong though....:)

Thanks Miha........

Miha Markic said:
Hi scorp,

There should be on Dateoforder column in dataset so it is right that there
is no Date column.
Can you show some code or explain the problem a bit more?

--
Miha Markic [MVP C#] - RightHand .NET consulting & software development
miha at rthand com
www.rthand.com

scorpion53061 said:
In this statement:

select CONVERT (CHAR(10), DATE, 101) AS DATEOFORDER

the dataset had it appear as "DATE" which was empty and as DATEOFORDER which
was as it should be.

If I try:
Dstran1.Tables(0).Columns.Remove("DATE")

it balks and says there is no column called "DATE"

I dont want to have an empty column so how should I get rid of it?
Click to expand...
Click to expand...
 
Back
Top