Click here to Skip to main content
15,900,110 members

Comments by Mr.McCloud (Top 16 by date)

Mr.McCloud 4-Jan-13 12:51pm View    
Alright, thanks for the advice on the concatenation. I never knew it was bad practice the way I've been doing it. I'll definitely start using a better method.

And I guess when it comes to the partial class, I was just hoping for an easy solution to my problem. I've never fully understood exactly how the VB.NET code that I used worked in the first place.

I think the best thing to do, is go back and first learn what the VB.NET code is actually doing, and then I can probably translate that logic somewhat into C#

Thanks for the help.
Mr.McCloud 3-Jan-13 17:27pm View    
Okay scratch that.

The inheriting works and FirstName and LastName are both now treated as objects in the table.
Mr.McCloud 3-Jan-13 17:11pm View    
It can't recognize FirstName and LastName as columns.

I don't think Employee in C# is actually referencing the Employee table like it does in VB.NET. I tried getting it to inherit from the Employee's table but its not an option to inherit from.

Do you know how I can make sure Employee is actually a partial class of the Employee table instead of just a new class?
Mr.McCloud 11-Oct-12 15:27pm View    
Alright, I've tried it and it works perfectly. Thanks for the help. Much appreciated.
Mr.McCloud 11-Oct-12 15:21pm View    
Hmmm, I think I'm getting it. Do you mean then that instead of declaring it at the top, I should declare it in the actual procedure its being called in?

By the way, thanks for the help so far.