Bypassing the Serialization Mechanism
As you have seen, the framework provides a default way to read and write data to and from files. Serializing through an archive object suits the needs of a great many applications. Such an application reads a file entirely into memory, lets the user update the file, and then writes the updated version to disk again.
However, some applications operate on data very differently, and for these applications serialization through an archive is not suitable. Examples include database programs, programs that edit only parts of large files, programs that write text-only files, and programs that share data files.
In these cases, you can override the function in a different way to mediate file actions through a object rather than a object.
You can use the Open, Read, Write, Close, and Seek member functions of class CFile to open a file, move the file pointer (seek) to a specific point in the file, read a record (a specified number of bytes) at that point, let the user update the record, then seek to the same point again and write the record back to the file. The framework will open the file for you, and you can use the GetFile member function of class CArchive to obtain a pointer to the CFile object. For even more sophisticated and flexible use, you can override the and member functions of class CWinApp. For more information, see class in the Class Library Reference.
In this scenario, your Serialize override does nothing, unless, for example, you want to have it read and write a file header to keep it up to date when the document closes.
For an example of such nonarchived processing, see the MFC Advanced Concepts sample .