Seattle NITS

As you can probably guess from the date, I'm back in Austin now. Boy, that was quite a tour around the NW...I already miss it, but I'm glad to be back.

The Seattle NITS went even better than Portland in my opinion - but that is probably because I didn't forget to install the .NET framework this time *laugh*. Again, a lot of very good questions - even more than Portland. In fact, after my .NET presentation, I answered questions until the next session, then went into the hall and continued answering them. That is a great feeling.

So I'm back and almost done digging myself out of the backlog of stuff from the last two weeks. Whew...

I'm hoping to give some more "useful" posts in the near future - maybe during the Xmas holidays when everyone else is out of the office (family in town this year so I'm not taking many days off). So, if there is anything you'd like to see, drop me a line.

Comments

[Robert Brown]

Hello Brian-

I chatted with you at the Seattle NITS in the hallway after your .NET discussion--we talked about a broken ActiveX link that was inconsistently disappearing when moving our LV app from one machine to another. We found the problem to be differing versions of the ActiveX DLL to which we were trying to link. Our vendor supplied us with multiple machines, but each of these machines had one of two possible versions of the DLL. This version number was not reflected in their filename convention, so we had thought all along that the versions were the same. However, after my discussion with you at Seattle NITS, we were motivated to dig deeper into the ActiveX DLL. We found that the Class Version, as found in the registry, was different from machine to machine (Class Version number was also different from the filename version). Reconciling all of the machines to the same Class Version fixed our problem. The lesson here is that configuration management is very important! I appreciate your time and input.

Sincerely,
Robert Brown
Vice President
System Design Sciences, LLC
www.sdsciences.com