>Hello Stephen,
>
>Love the ambiguous-ness. I've seen errors like this before, and they're usually related to something being passed to SQL that the server doesn't know what to do with, so it chokes.
>
>Checking the call stack, I see you're running into the concurrency message builder, which is going to try to pull messages from the back end (which is why it's running FillDataSet()).
>
>Look at how you have your error messaging set up, starting with mmMessageManager in the Mere Mortals Framework project. By default that object expects you to have an error table called Message with a PK field called MessagePK. If your database isn't set up that way... that's probably why you're getting that error. You can subclass that object and change the behavior.
>
>Make sure you read the devguide on how to replace the managers with your subclass. We've done that with this and a few other managers to get "more desirable" behavior.
>
>Hope that helps,
>---J

Thanks. I'll give that look at sooner or later. Right now I'm on another firetruck. Dealing with my first ever MM ver 4 app. And the darn builder blows up in making a dataenvironment in a bizObject.

This is so screwed from when I did the app, but that was 98,99 so machines and servers all change I guess.