We will want to divorce FVSOUT from processor and optimizer at some point if at all possible. It really is a beast of a database (huge) and there are few times when I haven’t needed to go look at the TREE table so not producing that is not really an option. There are lots of times when projects need to be moved around and shared among people (particularly when we get this out to managers) and they will not want the FVSOUT to be a requirement—An analyst can create a project and transfer it without the FVSOUT and a manager can run processor and optimizer to their hearts content—that’s the ideal.
After searching the code, I only found the reference to FVSOut.db in Processor that caused the error. I will remove this. There are no dependencies in Optimizer.
We will want to divorce FVSOUT from processor and optimizer at some point if at all possible. It really is a beast of a database (huge) and there are few times when I haven’t needed to go look at the TREE table so not producing that is not really an option. There are lots of times when projects need to be moved around and shared among people (particularly when we get this out to managers) and they will not want the FVSOUT to be a requirement—An analyst can create a project and transfer it without the FVSOUT and a manager can run processor and optimizer to their hearts content—that’s the ideal.
After searching the code, I only found the reference to FVSOut.db in Processor that caused the error. I will remove this. There are no dependencies in Optimizer.