Guys, I released another version last last night (or early this morning, depending on your perspective). Give that one a try, I fiddled with a lot of the train building code.
EDIT: Fred, I added the “Send DB” link on the help menu, maybe you can send me your database so I can take a look at it.
Ah…Bruce tracked down a bug for new cars. Working on it…
That’s a big bug Bruce :o So would that explain why if I delete all my cars then re-load them they don’ ever come in from off-layout ?
o do it 
They don’t want to be deleted again?
I think that’s one we’re chasing now…I’ve got it installed on another computer with a smaller layout.
They deleted fine and recreated in an older version. In V45 the system cant find them. The car report sez they are off layout.
Anyway - I’m still not having much luck with the latest build no matter which version of my database I use. It is still doing very odd stuff like taking two cars from the siding where a industry is and delivering them to the same industry.
Thinking that I may have royally screwed up the database by all the experiments I’ve been doing, I decided to start over from scratch. After backing up the data I Uninstalled TrainOps and deleted the data. I then reinstalled TrainOps and let it build an empty dayabase that I will manually re-load.
I was making a PDF of all the configuration screens from my old database when I screwed and lost about a half-hours worth of screen shots. I’ve lost my ambition to continue down that road tonight. Perhaps tomorrow when I’m getting paid to do it
Jon, yea, you really need to stop going back to an older version of the DB. I’ve changed keys and pointers and going back to a DB created by an earlier version will remove those changes.
Bob,
Updated to the latest, there is still something weird going on. I sent you the DB, could you please check train 5105 - the last portion when it picks up the tankers is really strange.
Bob McCown said:OK - It's done. I re-installed V45, built an empty DB and manually keyed in all of the setup.
Jon, yea, you really need to stop going back to an older version of the DB. I've changed keys and pointers and going back to a DB created by an earlier version will remove those changes.
I promise to delete all my old DB files and not go back
FYI - This newly created database is working much better than the one(s) with dubious linage. Off Layout cars actually show up in the Equipment Location screen as off-layout :o
So now that it’s doing more I have to go back and figure out how to best handle turns. Or perhaps, I don’t handle them at all, making every train return to it’s originating division.
What I think I need now most of all is Bruce’s document on the theory of what the program is designed to do (Sub title: That’s not a bug, it’s a feature!). I think you guys with lots of operating experience may just have this stuff in your heads and can logically decide how to route a train. I still need some help in that area.
Jon Radder said:Bob McCown said:OK - It's done. I re-installed V45, built an empty DB and manually keyed in all of the setup.
Jon, yea, you really need to stop going back to an older version of the DB. I've changed keys and pointers and going back to a DB created by an earlier version will remove those changes.I promise to delete all my old DB files and not go back
No. I was fooling around, saving old copies of the database and then bringing them back in after a version upgrade. If you have stayed with the same copy for the database since the beginning, each upgrade makes any necessary changes in the db the first time it starts.
I was circumventing that process and had to pay the price of re-keying the data. No one else should have to do that.
Hehehe, good thing I was warned before I implemented that routine! 
I knew better but Bob said it shouldn’t be a problem IF he didn’t change the database. So I took a gamble that it didn’t change and I lost. Stupid Tax has been paid (again) and life is good again.
What I have learned however is that you need to back up both the program and data together. If you must restore a backup, you need to restore the matching version of the program with it. Only then can you get the automatic program upgrade, which will also update the database.
Once Bob has all the operational issues under control it might be possible for the first entry in the database to be a version code. Then the program could automatically update old databases. I say this like I think the coding is easy, but I do realize that sometimes the little features are the hardest to implement.
Jon Radder said:Nothing is impossible for the person that doesn't have to do it. :D :D ;)
I say this like I think the coding is easy, but I do realize that sometimes the little features are the hardest to implement.
An interesting idea…
