Thank you Andrei, Speculator 152, and Rick for the suggestions. I have made notes on all of them, and will consider when we can work these items into our development schedule. I want to comment on a few items here: Andrei #1. We learned a lot from the experiences of the past few months and we are not going to disturb the core models any more. I want people to understand that we have 100’s of customers outside the John Locke group who see the shortcomings of the existing model, as do we, and we still feel that it is right to try to improve upon it. However, when we get ready to move forward, we will add a new model selection in the program. Maybe we will call the existing model that John Locke people need the “golden oldie” and the model that we want to move forward with will be called by some other name. #3. I assume you’re talking about importing trades from a TOS output file. I want to work on this very soon. #4. What data entry delays are you referring to? Is it trying to type something into the Matrix while receiving quotes from TOS? If so, I already spent a LOT of time trying to resolve that and could not. Somehow the old style DDE quotes interface interferes with keyboard input. I understand your other points. I’m giving thought to doing #7 sooon. Speculator 152 About the back-testing performance: Did you read what I wrote about this previously? We are taking action in this area. In UI, you suggested using a Ribbon style menu across the top. How do others feel about this? Is this one of the important things that you feel needs to change? I understand your other points. Rick #1. I don’t think people would appreciate having their strikes or expirations shifted automatically. They might be surprised or confused by it. #2. It sounds like you used the same R code for all the trades, which causes the program to consider them to be grouped together and considered a single position. #3. I tried stretching out the OpVue program across two monitors, placing several open windows scattered apart, and when I closed and re-opened the program, the windows opened up in the same positions. Please call for tech help if you need to. Andrei again. Regarding having all positions have their options automatically defined in the Matrix: This should work already, maybe not real-time though. You might need to close and re-open the Matrix. I’m going to make a note to check into this. Thanks. Now I’d like to respond to the comments about Delphi: There is a misconception among many that Delphi is an old style development system that is not staying current. The truth is, Delphi is a completely modern system, kept up to date by its relatively new owner, Embarcadero. With it, you can develop PC apps, web apps, and mobile apps. All sorts of modern controls can be popped into forms, so if you think OptionVue looks old fashioned, that would be my fault, not Delphi’s. And in terms of performance, programs compiled using Delphi rank very high in benchmark tests. We, at OptionVue, put it to the test every day in our servers which can handle bursts of up to 100,000 price updates per second arriving from our data source. Back in 1995, we selected Delphi over Microsoft Studio because there was a huge productivity difference. Not only did we find that we could write code faster in Delphi, but because the compiler was so much faster (3 seconds versus 2 minutes), debugging was much more pleasant as well. You could make a change and try it out in seconds, thus keeping your mind on the task. Anyone who prefers C++ over Pascal, you can get a C++ version of Delphi. My personal preference is Pascal, as I find it more readable, and programs written in Pascal are easier to maintain in my opinion. Both the server side (NetVue) and the client side (OptionVue) were written using Delphi, and the truth is, OptionVue Systems would not be here today if, back in 1995, we were forced to use Microsoft C, because our first Windows version of OptionVue would have taken too long to develop.