I'm using the trial version 5.x.

Currently I'm using the Diagram.SaveToStream(...) method to save my diagram to the database.

Now, if I go back and restore the diagram from the binary data stored in the database, then add more nodes, then save the diagram again using the Diagram.SaveToStream(...) method, the newly added nodes are missing the next time I try to reload the Diagram and it's back to the way it was the first time I created it.

I'm really at a loss for what's going on here.
Any suggestions would be appreciated.

Thanks.

Right now I'm using the Diagram.SaveToStream(...) method to save it and then using the Diagram.LoadFromStream(...) method to load it back. 

I'm not using a DataSet.  I'm using LINQ-SQL to save and load the diagram.  I have compared the two sets of binary data and they are different.  Also, I've noticed that if I save a diagram, then load the diagram then save the diagram, the binary data is different on the second save than from the first save, even though I didn't change anything.

In order to save and restore a diagram what must I do or what else might be the problem?

Thanks.

Here's the code I'm using to save to the database and read from the database
dc is a LINQ-SQL DataContext object.
rs is a variable that points to a LINQ generated class for a database table.  The table has several columns including one that is a Varbinary(MAX) that stores the binary representation of the diagram.

Saving a diagram:
....

//Save the diagram changes.
using (System.IO.MemoryStream ms = new System.IO.MemoryStream()) {
    this.Diagram.SaveToStream(ms, true);
    rs.Diagram = ms.ToArray();
}
dc.RS.InsertOnSubmit(rs);
dc.SubmitChanges();

....

Restoring a diagram:
....

using (System.IO.MemoryStream ms = new System.IO.MemoryStream(this.RS.Diagram.ToArray())) {
    this.Diagram.LoadFromStream(ms);
}

....

Thanks,
Mike

Yes on both accounts.
The InsertOnSubmit(...) method causes the the values to be submitted when SubmitChanges(...) method is executed.
There is no other record except the one I'm adding.  Prior to making/submitting these changes, I delete the previous table data (including the diagram bytes) and then recreate it and and store the new diagram bytes along with the other data.

Thanks.

After further testing, I have discovered that if I close my entire application down and then restart it, loading the diagram (without having loaded a previous diagram) the changes that I applied and stored in the database are now apparent.

It seems that the diagram needs to be cleared before changing with a new or different diagram.

Is there such a feature or is this a bug?

Thanks.

You know better about the internals of the methods than I do.  Nevertheless, I can only see the updated diagram changes if I close my entire application down and then restart it. 

If I follow these steps listed below with my diagram form up I can reproduce this problem:

1)  Start a new form with the diagram.
2)  Add some TableNodes to the diagram.
3)  Save the diagram.
4)  Load the saved diagram.
5)  Add some more TableNodes.
6)  Save the diagram.
7)  Load the saved diagram.  The previously added (step 5) TableNodes are missing.
8)  Close the entire application and start over, loading the previously created diagram (step 6).  The previously added (step 5) TableNodes are now visible.

Something is amiss here.  It may only be on my end, but it might not be.  It seems that if the Diagram control contained a previous diagram and then a new diagram was loaded, it keeps its previously loaded diagram over the newly loaded diagram.

This is a serious issue for me as I need these diagrams to be displayed properly.

Thanks.