Re: Modernization and multi-member files

[cfuture <cfuture@xxxxxxxxxxx>]

> > Simon Coulter wrote: There is nothing wrong with multi-member files as a solution to a problem. Not very relational but so what? That's not the only way to design a database. Multiple members can be handled quite well using OVRDBF and USROPN. Even SQL copes with them via OVRDBF or CREATE ALIAS, and multiple members are how Rochester chose to implement  partitioned data files so they can't be all bad.
> >     
...
Just one consideration was the management of source files/source 
members, IIRC, John Sears once said. (Although I think he also said he 
wasn't so sure it was a good idea..)

> Just out of morbid curiosity (it doesn't impact anything I'm currently doing, and I don't really have time to research it) what happens if you try and create logical and/or join-logical files based on multi-member physicals?
>   
...
You can make it as simple or as complicated as you like, each LFM 
accessing any combination of PFM's in any order.. I started to use it as 
a solution once but quickly quit, maintenace can get really crazy!

Combine that with multiple-format logicals and it gets /really/ crazy..

--Alan