[RESOLVED] [02/03] Maximum number of columns in a table?

[Redeye44us]

Hey everybody,

I have imported a database from AcuCOBOL into SQL 2005. I am able to work with it in SQL, but in VB.Net, when I try filling the table, it is unable to fill the table, but acts as if it does (no exception during fill). When I look in my locals at the table, many fields (like Rows) show "error: cannot obtain value" and the For Each loop I have does nothing even though there should be about 6000 rows. There are approx 370 columns in this table. Is there a max number of columns for tables that might be causing a problem? Any help would be greatly appreciated.

[Redeye44us]

Hello again,

I resolved the problem by only importing the fields I would actually be using. So, I don't know if it was the number of columns or something with one of the other fields. Oh well, moving on...

Thanks,
Joe

[jmcilhinney]

Maybe this is a one in a million situation but I can't think of any set of circumstances where a table with 370 columns would be a good thing. I would strongly suggest that you consider redesigning that database.

[Redeye44us]

I agree. The table is in a AcuCOBOL application I am working to replace with my VB app. It has been a pain to work with.