Jump to content
Xtreme .Net Talk

Recommended Posts

Posted

We're finding a situation where a dataset is failing, but when we remove a field or two from the select statement, it will work fine. Does anybody know if there is an explicit limit to the number of fields that can be handled by a dataset? This is really odd behavior, and I can't find any documentation that says one way or another.

 

Any ideas?

Posted

Didn't heard about it before but it sure take more time to analyse more field.

Let's say you have 75 fields and 200,000 records...

if you reduce 75 to 50... it sure take less time to proceed ! :)

 

However... what I suggest you, when you make select statement, to NEVER include SELECT *. If you update your DB, it will bring out more field than original. Always make sure to explicitly write in order the field that you want.

 

Stay Zen

 

If I didn't answer to your question... let me know

"If someone say : "Die mortal !"... don't stay to see if he isn't." - Unknown

"Learning to program is like going out with a new girl friend. There's always something that wasn't mentioned in the documentation..." - Me

"A drunk girl is like an animal... it scream at everything like a cat and roll in the grass like a dog." - Me after seeing my girlfriend drunk and some of her drunk friend.

C# TO VB TRANSLATOR

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...