Search results

  1. D

    Brain has abandoned me - return max date for each unique pair of foreign keys

    Thank you - that's what I was trying last night but wasn't able to put it together correctly. Out of curiosity, what pros/cons do you see to the multi-query approach vs what jdraw suggested above? My # of users/records is unlikely to get so large that the performance difference will be...
  2. D

    Brain has abandoned me - return max date for each unique pair of foreign keys

    YES! And all in one query. Thank you! Apologies for being slow, something came up right after I posted that had to be dealt with.
  3. D

    Brain has abandoned me - return max date for each unique pair of foreign keys

    My apologies, I didn't intend to post&ghost, something came up. I swear I did try this, but as I mentioned I had been at it too long and wasn't able to make it work.
  4. D

    Brain has abandoned me - return max date for each unique pair of foreign keys

    Happy whatever you celebrate to everyone! With the quiet holiday weeks I've been making long overdue progress on my EAV-based project, in fact I was hoping to post it for feedback soon, but I realized today I was making a simple mistake somewhere and apparently I've looked at it too many times...
  5. D

    Close form without saving record?

    Thanks Doc Man! GREAT breakdown.
  6. D

    Close form without saving record?

    @Pat Hartman : question on best practice, only tangentially related. In the above example, if ALL you needed to do was make sure the value for a given field is unique, is there a benefit to using a custom code in the BeforeUpdate (or even the form level ValidationRule property) vs. setting that...
  7. D

    Normalization / Approach question – arbitrary characteristics (ETA: Entity Attribute Value EAV)

    Thanks Pat, that's helpful/inspiring (also, good to chat with you again after my years away!). Forms and reporting are something I'm trying to keep in mind even as I'm sketching out structures, because it's a big factor here, which is one of the reasons I'm concerned about EAV - a lot of my...
  8. D

    Normalization / Approach question – arbitrary characteristics (ETA: Entity Attribute Value EAV)

    Thanks to you and to @gemma-the-husky - combining responses here. I've been reading up on EAVs where I can--of course once I knew what the silly thing was called I've found a lot of background reading out there, still trying to absorb/understand... I can see how, as you two outline, I could...
  9. D

    Normalization / Approach question – arbitrary characteristics (ETA: Entity Attribute Value EAV)

    Thanks - I'm going to check out @the_doc Sorry to be thick, but I'm not sure I see the difference between what you've outlined here and the third approach I described above - would you mind being more specific? I'm intrigued by the [edit] portion especially, is there a way to avoid the...
  10. D

    Normalization / Approach question – arbitrary characteristics (ETA: Entity Attribute Value EAV)

    I will definitely look for this - thank you! I'll circle back here when I've dug in a bit.
  11. D

    Normalization / Approach question – arbitrary characteristics (ETA: Entity Attribute Value EAV)

    Thanks - I'm going to check out @The_Doc_Man 's suggested research approach and then circle back. My main concerns about going this way are the need to me to write a new function everytime there's a new "answer type" needed, and the complexity of calling get/set every time anything gets...
  12. D

    Hello, Again!

    Don't feel bad, it was a LONG time ago.
  13. D

    Normalization / Approach question – arbitrary characteristics (ETA: Entity Attribute Value EAV)

    Greetings Access Wizards – been many years since I used Access, started to seem like the right tool again LAST February but then… well, you know, and my work shifted radically. Now things are getting back on track at my desk, so I’m again trying to scrape the rust off my brain. Which leads me to...
  14. D

    Hello, Again!

    Indeed, same screen name, though it's less applicable these days...
  15. D

    Hello, Again!

    Which is true of pretty much every part of my life two decades later :) Indeed I did, Doc Man, and I remember you as offering helpful feedback back in the day. I logged in every once in a while, often enough that my old account got moved over, apparently. I like the new digs! May take a bit...
  16. D

    Hello, Again!

    I was "here" a long, LONG time ago. At the time, Access was the answer I used for a number of work questions, mostly by the good graces of several members of this forum. I'll jot down the names I remember below. But, then, my work took a turn, and Access was no longer really a part of it. I...
  17. D

    It's 2020. So far, I'm not dead.

    It's 2020. So far, I'm not dead.
  18. D

    Of Saving Queries and Calculating Fields

    Thanks as always. You're the best! --Grateful-Yet-Again Mac
  19. D

    Can't make form visible, again

    Argh. I knew that. (begins writing 1,000 times: "must not rush replies...") Sometimes Access will hold off on screen updates if there is more code, and the .Repaint method forces an update. Sorry I'm not help today... --Abashed Mac
  20. D

    Of Saving Queries and Calculating Fields

    Pat: If you have a moment, could you expand on WHY this is considered "best practice"? I read a similar statement (by you, most likely) at some point and started basing every form on a query, especially in split FE/BE environments. Someone recently asked me why I didn't just base a form on...
Top Bottom