|
dandy72 wrote: increased by an equal amount
That doesn't sound right.
|
|
|
|
|
What I think I should've said here is that if Bob (worth 15%) dies, and there's 15 people left on the list, Bob's 15% should be redistributed equally among those 15 people - so each person gets an extra 1%. If there's 30 people, they all get an extra 0.5%.
|
|
|
|
|
That's what I thought, but it seems to me that if Alice is due a 50% share of T, that she should get 50% of Bob's 15% share of T.
|
|
|
|
|
dandy72 wrote: increased by an equal amount?
That would depend on cause of death and amount of involvement by the survivors wouldn't it? That would make the equation even more complex.
The less you need, the more you have.
Even a blind squirrel gets a nut...occasionally.
JaxCoder.com
|
|
|
|
|
Well, I mean, remove the others from contention first...
|
|
|
|
|
Here's one way: deathInheritance.xlsx (9.5 KB). If you drag the middle rows out, or delete them, you can see how things change. You might have to readadjust the calculation to distribute differently.
|
|
|
|
|
Nice. I just might use that, or adapt mine to do something similar (I haven't yet looked at it...)
|
|
|
|
|
|
Don't think of the 15% as a percentage, but a proportion of the total.
So to calculate how much each person gets, add up all the proportions, to give a total 'proportion'.
Then for each person, the amount they get is (their 'proportion' * total inheritance)/(total 'proportion').
Then deleting a person from the spreadsheet when they die, will increase the others inheritance according to their proportion.
|
|
|
|
|
I figured using a "fixed" percentage wasn't going to be solution as it needs to be changed when someone dies. I'll rework it with your answer in mind. Thanks!
|
|
|
|
|
Having business critical logic in spreadsheets should be (and maybe is?) considered an anti-pattern.
A big part of my job is actually replacing Excel files that specific people know how to use, but no one knows how they work.
When these specific people are somehow unable to do their job, a lot of work isn't done, isn't done correctly and/or isn't done fast enough.
It's a huge risk for companies, but unfortunately things often have to go bad before they start thinking about replacing Excel files
I get it though, Excel can do a lot and costs a little.
It's a live-saver, especially for smaller organizations.
There's probably a graph somewhere with the usefulness vs. liability of an Excel spreadsheet compared to the size of the organization.
For small companies the usefulness far outweighs the liability, but the bigger the organization becomes the bigger the liability and the smaller the usefulness until the liability becomes greater (but of course they'll keep using it for another 20 years or so).
|
|
|
|
|
And it becomes the users hammer when their need is not met by their IT shop.
MS Access the same. Their project doesn't make the cut for time or money, and they have the skills.
And, Excel allows them to put text in what should be a number field. Those pesky databases with all the rules ...
|
|
|
|
|
Why delete Bob's row if he dies? Why not just mark him as deceased and change his percentage to zero? Wouldn't that cause the percentages to automatically recalculate?
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
That's the problem with the spreadsheet as it exists right now, percentages are "fixed", but need to be recalculated when someone dies. For simplicity's sake - assuming Bob (worth 15%) dies, and that still leaves 15 people alive on the list, then each one of them gets an additional 1% (15% / 15 people). If there's 30 people still alive, each gets an additional 0.5%. I'm not sure if I had conveyed that properly in my initial post...
|
|
|
|
|
I may be totally wrong, but my initial logic says that if you add up the "percentages" column and then give each person T x "MyPercentage"/"TotalPercentages" it will keep the proportions if one or more lines are deleted/cleared, or even added.
So old that I did my first coding in octal via switches on a DEC PDP 8
|
|
|
|
|
If it can tell me that, why can't it make that a clickable so I can see what my reply was???
Or am I just too old to intuit what I want to see from a Microsoft product?
|
|
|
|
|
If Microsoft wanted you to intuit what you want to see from a Microsoft product, they would let you know what you want to see from a Microsoft product.
|
|
|
|
|
|
kmoorevs wrote: have they embedded AI into everything?! From what I can tell, yes.
|
|
|
|
|
kmoorevs wrote: In fact, it almost seems to be getting better with use.
I suspect it has something to do with Microsoft buying SwiftKey keyboard. I am using it since it was provided by a small group and was paid. Only mobile app I ever paid for. It does exactly what you are talking about and has been doing it for years now. It knows how I talk to people.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
It can, but it's not directly obvious.
When you click an email (and when you group conversations, I guess), you can click the little > sign in front of the message.
This will show the entire conversation history, as well as your reply or replies.
Hope that helps.
|
|
|
|
|
yep what Sander said. Only problem is it sometimes closes the message you were working on or at least hides it.
To err is human to really elephant it up you need a computer
|
|
|
|
|
Started this morning, created a new basic class, added IEnumerable<T> to it, implemented teh required interface methods via VS, added tiny fragment of code to each method:
public IEnumerator<int> GetEnumerator()
{
for (int i = Min; i <= Max; i++)
{
yield return i;
}
}
IEnumerator IEnumerable.GetEnumerator()
{
return this.GetEnumerator();
}
And tested it.
It works: foreach and Linq all work perfectly.
Why was it a problem? Because I added IEnumerable to the class first yesterday, and that confuses the issue when you try to add IEnumerable<T> later ...
Now I can rip out all the enumeration code from the "real" classes and do the job simply.
Sometimes, I get too focussed on what I am doing to see the wood for the trees ... or I'm an idiot. Both, possibly.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I seem to solve my most challenging problems right after a good night sleep. What is weird is that the answer is revealed to me at the exact moment I start to wake up, but I am still not fully awake yet.
I also read, and believe, that a great deal of medical issues that affect us are due to a continual lack of effective, restorative sleep.
|
|
|
|
|
Last working day of 2021... I've got this issue I want to fix before my Christmas break.
Hours of debugging, but nothing.
It's something I've done countless of times before, send a file from an HTML form to my back-end, doesn't work.
Checked my code, my types, my inputs, went back to square one, copy/pasted code where I'm already doing it, nothing seemed to work...
Decided to give up, enjoy my vacation and fix it in 2022.
Januari 3rd, I hadn't thought about the problem for two weeks.
I start up my laptop, go into the code and almost mindlessly add enctype="multipart/form-data" to the form element.
Problem solved in < 1 minute
|
|
|
|