Thread:Mainframebabe/@comment-31592479-20180418162557/@comment-29954643-20180419175129

Oh, I think that It is highly likely that once you do open a dialogue box, a background copy of the page as it stood when you opened that dialogue would be saved as a temp file so that others could do the same thing. But once someone else posts, then the live thread is altered. And it might not be you alone that could lose your post in that circumstance. I have checked that scenario specifically but it isn't always true that when you refresh the thread you are working on, that a new comment (that wasn't there before) appears, but sometimes it does. Also, if it gets confused by temp file merges, the system default could easily be to simply dump all of the temp pages and restore keeping only the published threads as they were before. But I do get a 'technical feeling' that this is where it seems to go awry but I would have to see the code to see how the timestamp checking takes place to isolate why there is overlap, and, of course, this isn't my job and I am not getting paid to think this analytically anymore anyway LOL

Forget the silliness of the wiki and it's 'snake pit', how have you been? It seems that you are involved more in the forecasting angle in your business. You may not be 'closing books' anymore, but those closed quarter data is always paramount when discussing future trends and forecasting expenses and/or plans like 'closing down an existing service or product line'.

Business is business, no matter the widget (which could be a product, a service, or a combination of the two, I never cared which). I once had to write an executive forecasting model/tool (I think it was for Mattel, if memory serves). It turned out great. I wonder if they are still using my tool there LOL. I have found pieces of my code all over the place years later. Just plucked from somewhere else in the system and plugged (my comments and all) into other spots or used as stored procedures. I have friends that still call when they have come across a patch of 'El code' LOL. It is always worth a laugh or two. When I read in the paper (or on the internet nowadays) about a system that has been entirely replaced, I get a little sad, because I remember how much blood, sweat and tears, went into that system. I can usually tell just by reading the article how much of my code went by the wayside during that implementation. I take pleasure in knowing that any new implementation required a full understanding of what was there before and that my constant and consistent commenting helped the new programmer understand what each coded segment was doing, As is the case here, my commenting was prolific. Appreciated or not, at least it was paid for LOL

Given what you have just said, I shall make a copy of this diatribe before posting, just in case. Keep in touch and keep on editing. 👩‍❤️‍💋‍👩💋🌹🌻🌼💋 - El