Faced with a migration from your current software package? Lost a client to Oracle, SAP, Quckbooks? Many MV shops lose the war because they aren’t invited to the battles. And sometimes even the people who win wind up losing. There is a better way.
Why do I suddenly feel like someone just asked me if this computer thing will really catch on, or if water is a good idea?
A recent forum posting said the D3 Reference Manual is "confused" about which %functions are for Unix and which are for Windows. I have a lot of comments on this topic but with just a couple minor exceptions I disagree with the statement that the doc is really "confused" anymore.
One of our colleagues asked a good question in a forum yesterday about when to use UnNamed Common vs Named Common in Pick BASIC programs. I thought this would be a good opportunity to post some detailed information to the MV category here in the blog so that everyone could see it.
It’s started - people are getting more comfortable with DesignBais, learning the strengths and how to deal with the weaknesses. When the first release of a new application UI is in production and developers look back to see what they can do better (and respond to the end-user enhancement requests), they’re starting to get creative, get more out of the software, make it do things that isn’t in the documentation. And now the question has come up in the DesignBais forum - "should" we be coding into the internals of DesignBais? Here are my thoughts.
For those of us who sometimes enjoy a little sophomoric humor: 
I just had a situation with DesignBais connecting to two servers. Huh? 
Problem solved!
This article is in response to an inquiry in the U2 forum. I think a lot of people are curious about this, though it’s been discussed many times in various forums - and over many meals by some of us…
My first book, Using DesignBais, will be available soon. Here’s the current status. Comments and suggestions welcome.
A user in the DesignBais forum asked if there was a way to use a Header Process to put data at the bottom of an MV grid, rather than changing the value of the currently selected MV value. This was a fun and challenging problem, and I have a solution. I don’t know if it’s the right one. But it works! 