The extra cup of coffee helped. 

public override MicroFour.StrataFrame.Data.SaveUndoResult Save(bool Transactional)
{
    NextIDBO mNextIDBO = new NextIDBO();
    this.CustID = mNextIDBO.GetNextID("CM");
    return base.Save(Transactional);
}

If there is a sproc involved in the retrieval of the ID, and I am wrapping the save in a transaction, if the save fails will the rollback involve the NextIDBO sproc call, too?  I assume that it will, but I'd like to be sure.

Also, after playing with the syntax of the NextIDBO, I came up with this:

public int GetNextID(string pRecordType)
{
    int mNextID = (int)ExecuteScalar("spx_GetNextID('" + pRecordType + "')");
    return mNextID;
}

I really thought there would be more to it.  Naturally, the spx_GetNextID references the sproc to retrieve and update the ID number.  Is this really all I have to do to make this incremental non-primary key field to update (and any others in the app, too)?  If so, I am blown away.

When implementing the next ID for a non-primary key field, I would like to retrieve that incremental number during the save rather than at the SetDefaultValues (see thread).  Here is what I did in my CustomersBO:

public override MicroFour.StrataFrame.Data.SaveUndoResult Save()
{
    this.CustID = NextIDBO.GetNextID("CM");
    return base.Save();
}

Is that right?

Then, within the NextIDBO, I am attempting to implement the function that will return the next ID based on the ID type passed in the argument.  I am running into a syntax hurdle.  For some reason, a public method in my NextIDBO cannot be seen by the CustomersBO.  The function looks like this (full implementation code stripped for simplicity):

public int GetNextID(string pRecordType)
{
    int mNextID = 0;
    return mNextID;
}

Within this function I would run the appropriate stored procedure that returns a scalar value representing the next ID for the new record.  Perhaps I have not had enough coffee this morning.  What am I missing in the BOs so that the one can see the public method of the other?

Thanks,
Bill