Saturday, January 20, 2007

MOSS and ASP.Net 2.0

I'm working on an application and we are using User Controls hosted in an ASP.Net 2.0 Web Part. Everything was working fine then suddenly nothing seemed to work right. The form view controls were either outright broken, or the we saving blank rows to the database. It took some investigating, but here is what I discovered:

1. You cannot have an Object Data Source running on MOSS and it have a parameter (insert, update or otherwise) with a type of 'object'. This appears to be the type assigned for GUIDs (database fields of type 'unique identifier'). When you do, as soon as I would bind the formview I would get a generic MOSS error page. You know the one, 'A web part is causing a problem....'
By changing the type on the parameter to 'string' everything started working. Of course that was only half the problem. Since making this change eliminated the MOSS error but I was still getting blank rows in the database.

2. The other thing I discovered. You cannot use the asp:table control in templates of the form view. When you do, the data fields are no longer bound to the datasource. The asp:table is bound. The controls of the form view are now children of the asp:table and not the form view. You could probably get around this by fully qualifying the controls for the parameters but why?

So, we changed the templates back to straight HTML tables and changed the parameter types to strings and voila! The app is working as it should.

Now keep in mind that outside off MOSS the app worked fine without changing the parameter types. The asp:tables were still an issue thou.

Weird no?

Wednesday, January 17, 2007

Oh no he didn't!

Well, thank you very much Mr. Shupps (and Mr. Bowman too I'll bet!). So what are five things that people don't know about me that aren't either a) embarrassing or b) still subject to a statute of limitations? How about these:

1) I was in college for 9 years, and I am NOT a doctor. Now some of you may think that a statement like that is quite embarrassing, but you would be wrong. Dead wrong. It's just that I spent a couple of years deciding if computers were my true love (they are BTW, just ask my wife). Then I worked a full time career while trying to finish up my degree. Now 24k dollars and 240 credit hours later I hold a Bachelor of Science in Information Systems degree from the University of Texas. Yes, I could probably also hold a BA in Management, Account and Marketing (not to mention psychology [it's a long story]) with all those hours but thems the facts.

2) I am a huge gadget freak. I mean HUGE with all caps! I don't talk much about it in my blog so most of you probably don't know that yet. But if you saw my study you'd think eBay exploded all over it.

3) My first job was at Six Flags. There I said it. It's not on my resume and I don't speak of it often. When I turned fifteen I took a job at Six Flags Over Texas. It was a magical summer of standing in a store by myself with no way to pee for 6 hours at a time. Ahhh memories.

4) I have never been to Europe. It's a lame one but I'm running out of good stuff. Sorry. I hope to go sometime in the next two years. Otherwise I'll have to make do with the subject of number 5. Can't stand the wait, then lets go...

5) I have been to Disney World 10 times in 8 years (and almost no place else). Sound crazy, well yeah it probably is. My wife's family LOVES Disney World. And they work for an airline (initials AA, good luck figuring that out suckers!) so airfare is not an issue. They go for every vacation, and we didn't have kids in the family at all most of that time. Yeah that's right we went for ourselves, just the adults. And it rocked! I am a convert. I even have clothes with Mickey Mouse on them (ok, now that is embarrassing).

Well, there you have it. Enjoy. If I find anyone who has NOT been it yet I'll tag 'em. Otherwise it dies with me.

Goodnight.