Yes, unless there is another version released later than November 2008. The dates of MM dlls installed in PC are November 5, 2008 some are November 8, 2008.

>Jess,
>
>You ask "How Stable is MM3.5?". The answer is it is stable for me. There were a couple of hot fixes and I am wondering if the version you are using is the latest.
>
>Tim
>
>>Using MM.NET 2.3 in our company, all was well as far as software development is concerned but when we switched to MM3.5, most of the modules that work well before are no longer properly working. BTW, we are using VS2008 and Infragistics Framework for the UI.
>>
>>1. The mmInfra.CheckBox does not seem recognize boolean type because it does not save the value upon saving though equivalent business object is bound to the control. What we do for now is to manually assign to mmInfra.CheckBox the value of the business object just to display it and manually assign the checkbox control value to the business object when saving.
>>

>>when saving:
>>oCustomers.Entity.IsTheHorseDead = (bool)chkIsBooleanType.Value;
>>
>>when displaying:
>>chkIsBooleanType.Value = (bool)oCustomers.Entity.isTheHorseDead;
>>

>>
>>2. Using different business objects save methods for different scenarios. Controls are binded to the registered business objects.
>>
>> Steps:
>> Scene 1: Creation of new records
>> - Call the registered business objects “NewRow()” Method.
>> - Populate the entity fields.
>> - Call the mmBusinessForm’s “Save(BusinessObject)” Method.
>>
>> Scene 2: Updating of existing records.
>> - Retrieve data using a custom method that fills the business objects current dataset, using the business objects
>> “GetDataSet()” Method
>> - Update the entity field’s value.
>> - Call the mmBusinessForm’s “Save(BusinessObject)” Method.
>>
>> Expected Results:
>> Changes made to the business objects current dataset should be committed to the database, regardless if it’s a new
>> record or a record that needs to be updated, upon using the mmBusinessForm’s “Save(BusinessObjects)”. This
>> approach works on the previous version of MM.NET which is version 2.3.
>>
>> Actual Results:
>> When saving a new record (refer to scene 1) using “SaveEntity()” Method the compiler returns an exception saying “Object
>> reference not set to an instance of an object”.
>> When updating an existing record(refer to scene 2) using the mmBusinessForm’s “Save(BusinessObjects)”. The compiler
>> returns and exception saying “Object reference not set to an instance of an object”.
>>
>> Workaround
>> Checked the current saving scenario, use the method that works for each.
>>

>>if (accessmode == add)
>>       this.Save();
>>else
>>       SaveEntity();
>>

>>
>>3. When generating a new set of business object more than once.
>>
>> Steps:
>> 1. Generate a new set business objects for the 1st time
>> 2. Generate another new set of business objects for the 2nd time.
>>
>> Expected Result:
>> 1. Business objects should be generated successfully, regardless how many times you generate a business object.
>>
>> Actual Result:
>> 2. 1st time generation of business objects is successful, but the succeeding business objects generation fails. Visual Studio will display an error dialog; “Object reference not set to an instance of an object”.
>>
>> Workaround:
>> Restart Visual Studio.
>>
>>4.