RE: creating a view

I'm in the process of redefining files via DDL instead of DDS (that's
another thread). I've just really gotten started and have a long way to go.
I'm saving the more 'challenging' files until later. I have a few files
that are multi-member.

One example is the inventory transaction file. A lot of our inventory
transactions (receipts, adjustments, returns, transfers, etc) are handled in
batches. When someone wants to do inventory transactions, a member is added
to that file, the name of the member is the workstation (job) name. In this
way, any number of users can be doing inventory transactions at the same
time without any interference with each other. I know a lot of people don't
like multi-member files, and it may not be 'pure' from a database
perspective, but from a _business_ perspective, it works great here. (And
after all, source files are multi-member.)

I know I can't convert that file to DDL the way things stand now. I _could_
create many file objects to keep batches separate, but creating and deleting
objects is far less efficient for i5/os vs add/remove member. By delaying
this and other multi-member files until the bitter end, maybe I'll get
smarter, or have an aha! moment, or just decide to leave this file DDS.

Aside:
My big holdup right now is the file level check difference between DDL/DDS
when there's an *ISO date field in the record. I have an open PMR, and the
developer knows there's a high level of interest on this forum, so he will
be under much scrutiny. (his word, not mine <g> )