Hello, Stan

I haven't noticed the save code making cycles the way you describe them. Can you post the error stack? Also, do you have any code that calls SaveDataSet() or are you relying solely on the button's Click event?

---J

>btnSave on the form does not always save correctly. I receive the following message:
>“A floating point exception occurred in the user process. Current transaction is canceled.”
>Any ideas?
>On the Business tier, I have the business object that it is bound to, a typed dataset, and a dataAdapter. BTW, I have 4 databases (3 SQL Server DB's, 1 Access) and each business class is a subclass of a class which is tied to one of the four databases.
>When the object is first instantiated on the UI, it seems to make three cycles through the middle tier object, once for the underlying table in the base class, another cycle for the adapter, and a third cycle for the typed dataset.
>Which path does does the 'Save' take and does the dataset get reset (AcceptChanges set) but get confused on the second and third cycle (AcceptChanges is true) so the transaction is rolled back and nothing is saved?
>Thanks!
>StanB