>Are there real disadvantages to having, say, 12-15 memo fields in a VFP 6.0 table structure? In the past I know there have been problems with pointers being out of sync and other things. Is this still an issue to be concerned about in planning a table structure?

I would suspect not. If for no other reason, remember that forms, class libraries, and other structures in VFP development are actually .dbf files in disguise, and the majority of the fields in them are memo fields. So if there is a problem with memo fields, Microsoft is taking as much a chance with them as we ever would.

But I'd still recommend a reasonable maintenance cycle.