Getting old :-( (3 Viewers)

[BlueSpruce]

If you feel a pain in your chest (even if for just 5 seconds), don’t ignore it. The same is true for other symptoms.

I didn't suffer any heart attacks until I was 64. I had a feeling it was going to happen because repeated tests showed my lipids were high. Sure enough, in 2021 they rushed me to the cath lab and removed a blob of cholesterol that was blocking 99% of blood flow in my left anterior descending artery, causing a tear which they spliced up with overlapping stents. Now my EF averages 60-65% in the last stress test.

 

[The_Doc_Man]

Are you taking Mounjaro, or some other GLP for weight loss?.. I'm on Mounjaro 10mg x1 weekly and have lost 50 lbs, and counting. Currently at 210, goal is 190. It works!

I take none of the weight-loss drugs. No semaglutide, no GLP-anything, no Wegovy or Mounjaro. Weight loss by diet and exercise. Slow, because I react VERY BADLY to crash diets. But I'm working on it without extreme measures. With a slow weight loss, I can avoid the incredible binges that were a sad part of my life before I made the decision that it was time to stop the out-of-control weight gains.

I now allow myself certain treats, but not as many of them. Now I use them to avoid binges.

 

[BlueSpruce]

I take none of the weight-loss drugs. No semaglutide, no GLP-anything, no Wegovy or Mounjaro. Weight loss by diet and exercise. Slow, because I react VERY BADLY to crash diets. But I'm working on it without extreme measures. With a slow weight loss, I can avoid the incredible binges that were a sad part of my life before I made the decision that it was time to stop the out-of-control weight gains.

I now allow myself certain treats, but not as many of them. Now I use them to avoid binges.

I tried loosing weight without the meds, but was unable to control my craving appetite.

 

[BlueSpruce]

I was about to post a thread asking for help in identifying how I managed to make text in a report control bold, if the person had passed away.

I compacted the DB and was about to attach it to the post.

I had looked (what I thought was ) everywhere, and could not find how I did it. Nothing in CF at all?

Just as I was about to attach the DB, I suddenly thought of one last place.

Yep, in the Detail_Format event.

Getting back on topic with the OP, if you didn't use conditional formatting based on the presence of a date in the Date of Death field, how were you able to display persons data in bold text if they're dead?

 

[DHookom]

Getting back on topic with the OP, if you didn't use conditional formatting based on the presence of a date in the Date of Death field, how were you able to display persons data in bold text if they're dead?

I would use code like:

Private Sub Detail_Format(Cancel As Integer, FormatCount As Integer)
    Me.Last_Name.FontBold = Not IsNull(Me.DateOfDeath)   
End Sub

 

[Gasman]

I would use code like:

Private Sub Detail_Format(Cancel As Integer, FormatCount As Integer)
    Me.Last_Name.FontBold = Not IsNull(Me.DateOfDeath)  
End Sub

I used something similar, but with that logic.

 

[The_Doc_Man]

In my genealogy database, sometimes I don't get a date of death even though the date of birth is over 100 years ago. Therefore, I included a flag for "presumed dead." But my DOB for "unknown" is 1/1/100 and my DOD for "unknown" is 12/31/9999.

 

[Gasman]

Would that be 01/01/1900 Doc?

 

[The_Doc_Man]

No, the earliest date that can be expressed in Access is 1/1/100 (CE). I figure if I show a date more than 2000 years ago, anyone born then is dead by now. But seriously, the problem is that date CDATE(0) is in 1899, which is within the range of dates I might see for my grandparents, great-aunts and great-uncles, and miscellaneous other persons. I don't want an accidental date in a relevant time range - so my "way too early" date is as I stated. Remember, I was talking about a genealogy project - for which I've hit dates as far back as the early 1600s. A date of 0 is useless to me except if I actually DID have an event that occurred in late December, 1899.

 

[BlueSpruce]

No, the earliest date that can be expressed in Access is 1/1/100 (CE). I figure if I show a date more than 2000 years ago, anyone born then is dead by now. But seriously, the problem is that date CDATE(0) is in 1899, which is within the range of dates I might see for my grandparents, great-aunts and great-uncles, and miscellaneous other persons. I don't want an accidental date in a relevant time range - so my "way too early" date is as I stated. Remember, I was talking about a genealogy project - for which I've hit dates as far back as the early 1600s. A date of 0 is useless to me except if I actually DID have an event that occurred in late December, 1899.

Can you replace those placeholder dates with a value in an additional LongInt or text field? Are you going to be doing any date arithmetic with DoB, DoD? How do archeological and astronomy apps deal with really old dates?

 

[The_Doc_Man]

It's just that a test for "date too far back" is just as easy against #1/1/100# as it is for #12/30/1899# - either constant works in comparisons. However, when looking backwards a few generations from members of my current generation, I'm more likely to accidentally run into #12/30/1899# than the other date and get a false negative.

It's easy enough, though, to have that date that way. Public Const MinDate As Date = #1/1/100# works just fine and date comparisons love it.

 

[BlueSpruce]

It's just that a test for "date too far back" is just as easy against #1/1/100# as it is for #12/30/1899# - either constant works in comparisons. However, when looking backwards a few generations from members of my current generation, I'm more likely to accidentally run into #12/30/1899# than the other date and get a false negative.

It's easy enough, though, to have that date that way. Public Const MinDate As Date = #1/1/100# works just fine and date comparisons love it.

Understood, however it would be nice to, for example, filter on the 17th Century to see which members were alive during that era. For my ancestors, I created tables that show their age throughout different years of their lives so I can visualize what world and personal events they were experiencing as they aged. This is my Dad's table.

 

[The_Doc_Man]

Understood, however it would be nice to, for example, filter on the 17th Century to see which members were alive during that era.

I can do that with my current setup. In fact, the end of the 16th century is as far back as I've gone in any branch. My biggest problem is that a lot of times, the data available to me is from a church ledger and it tells me NOTHING about the person, only location, birth, and death. Which is why I'm moving on towards winding down the Ancestry subscription. Too expensive to keep much longer.

 

[BlueSpruce]

I can do that with my current setup. In fact, the end of the 16th century is as far back as I've gone in any branch. My biggest problem is that a lot of times, the data available to me is from a church ledger and it tells me NOTHING about the person, only location, birth, and death. Which is why I'm moving on towards winding down the Ancestry subscription. Too expensive to keep much longer.

500 years from now our descendants will know a lot of details about us. They will view videos of how this world was. They might also have discovered how to travel back in time. The UFO's people have claimed they've seen could be humans who have traveled back to our time.