I have an application under development that will use ES. I have it up and running and everything is fine, great product. Beta and release wont be long now.

Now, part of this application includes storing scanned images as multi-page Tiff files. I have a varbinary field set up to store them, and I have decided to use the byte array method and simply translate the images as needed, my BO field property reflects this and returns byte() only. Out of this two questions if I may.

1) since the image data is not being serialized (or is ES doing it behind the scenes anyhow?), thus having the additional overhead, would I still benefit from turning on custom serialization versus the default? I am just worried about the image data, the rest of the app runs fine without it. Even the images are acceptable coming down from ES, but who wouldnt want 90% less coming down the wire (from help docs), right?

2) Does turning on custom serialization in any way effect how the data is stored and the ability to "flip the switch" to use ES or local access within the application? Right now I develop locally, and at the end of each day test what I have done by restoring the local SQL database to the ES server and running the new features/code. This product will also need to run run both locally and via ES depending on the client. My admittedly limited understanding of ES is that the data is transmitted as binary data and then reconstructed upon reaching the ES for commit to the ES database, having no actually effect on the stored data at all, correct?

If you think I might benefit from customized serialization... I am getting an error when I add this line to my appmain as described in the help file.

Code: MicroFour.StrataFrame.Data.Enterprise.RequestProcessor.UseCustomDataSerializer = True

Error: "RequestProcessor is not a member of Enterprise"

Thanks

Keith Chisarik