I wanted to have a look at your new TDBAdvRichEditor today so I hooked one up to an Aurelius blob field and tried to save some text but it saved "TPF0TStateSaver" instead of my text then give me "Argument out of range." when I came to open the table again. Is there something obvious I am doing wrong? I just dropped the component on the form and set the datasource and field name. It works fine if I save/load to a TDBmemo.
The data persisted from a TDBAdvRichEditor represents the formatted text in binary format. You can consider it as a collection of objects. The first object in the stream is a TStateSaver object, but many other objects are added after this in the stream. If TDBAdvRichEditor loads this persisted stream again, the formatted text should appear but of course, this formatted text will be unreadable from another control that can only handle plain text.
HI Bruno,
Yes I get that about the collection of objects but there appears to be a problem reading or writing from the component to the blob as I can post it scroll back and forth in the dataset all without problem but if I close and re-open the form I get "Argument out of range" (the exception is raised in System.Classes.Treader.ReadRootComponent). I don't get that problem if I replace the control with a DBmemo.
However I tried to do a little test app to send the code to you to demonstrate the problem and I couldn't replicate it. Really I was just investigating what the component can do so it's not causing me any problems in production code. I only posted here just in case there was something obvious I was doing wrong. Just one to make a mental note of in case it comes up with someone else.
As always your help is much appreciated, thanks again Bruno.
A test to see if your DB isn't messing with the stream could be to do a DBAdvRichEditor.SaveToStream and then also read the blob data back from the DB field as stream and compare these two streams. They should be identical. If not, I can only suspect the DB can't handle specific values in the stream. Notice that this is a binary stream, so if your DB has a restriction with respect to accepted chars in the blob, that could be an issue.