Well, I agree with you. I don't think this is a simple task and I have not
ever heard of it being done before.
I will provide some background on the project:
-It is an investment system used to monitor trading activity for a company.
-It is currently a legacy mainframe COBOL system that is attempted to be
re-written.
-We have 5 developers with little PB & HOW experience. Two have 4+ years of
PB4 and three have less than 1 years using PB6.
-The detail of what we need for the effective dating is that each table would
have a version number, effective start date, effective end date, process
start date, and a process end date. The idea would be to use associative
tables to join individual tables. It has been brought up that ALL tables
would have these fields. This would include any infrastructure tables. I
don't see why this would be needed.
-One are I see where this would be a problem would be with code tables. We
would have no foreign keys in the database. If we use these on dropdowns, I
don't see how it would work.
Any input would be appreciated.
Thanks
ML Roberts
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
