Bob,

If you want to try something just for grins, try changing your code below to the a variation I posted just below.


>
>I have a FirmAcct business object and I run the following test bench code:
>
>

>FirmAcct oFirmAcct = new FirmAcct();
>            FirmAcctDefaults FAD = new FirmAcctDefaults(businessID, firmID);
>            oFirmAcct.NewEntity(FAD);
>            oFirmAcct.Entity.FirmAcctBankAcctNbr = bankacctNbr;
>            oFirmAcct.Entity.FirmAcctName = firmacctname;
>            oFirmAcct.SaveEntity();
>            return oFirmAcct.Rules.GetAllBrokenRules();
>

>

FirmAcct oFirmAcct = new FirmAcct();
     FirmAcctDefaults FAD = new FirmAcctDefaults(buisnessID, firmID);
     FirmAcctEntity faEntity = oFirmAcct.NewEntity(FAD);
     faEntity.FirmAcctBankAcctNbr = bankacctNbr;
     faEntity.FirmAcctName = firmacctname;
     mmSaveDataResult result = oFirmAcct.SaveEntity(faEntity);
     if (result == mmSaveDataResult.RulesPassed)
     // just a place to put a break point if you want to see the result value.

I am just wondering if you have more explicit control over the entity object maybe it would be different. I have no idea why that is happening given it doesn't give that issue on another machine and you have no code changes or version changes. That doesn't make any sense. Sometimes I just have to try things to either confirm or rule out something. That was why I suggested a different project test just to rule out the process works on this windows 7 box even though that is sort of a far reach. If you try this, it may give a clue also. Maybe Kevin will have something different for you.
Tim