Search results

  1. Papa_Bear1

    Data Macro triggers/fires only under certain circumstances

    I do have the system set up in the normal way - with shared data in the back-end etc. etc. Most users will be doing the usual 'thing', running queries and generating their own output etc., based on data in the shared tables. But one user will be managing the input to this system, and this was...
  2. Papa_Bear1

    Data Macro triggers/fires only under certain circumstances

    Yeah- I agree - it is indeed weird. I don't even really like it since the back-end is linking to a table in the front-end. But since I know I'll have only one Admin - or certainly only one Admin at a time, it seemed OK to have the back-end reach back and link to the front-end for this purpose...
  3. Papa_Bear1

    Data Macro triggers/fires only under certain circumstances

    Hi jdraw - thanks for asking... Yes - it is a split database, and normally you have the linkages from front-end to back-end tables. In this case, I have a bunch of code in the back-end that updates the shared data, but I was trying to keep all users connected via the front-end, including the...
  4. Papa_Bear1

    Data Macro triggers/fires only under certain circumstances

    I'm trying to use "data macros" as a basis for performing a trigger-like action in Access (365). Ordinarily I might do this simply with an "After Update" event on the field of interest with some VBA etc., but in this case, I have a split database, where code is running in the back-end, and I'm...
  5. Papa_Bear1

    What's your best/worst joke?

    This is for bad jokes? OK: . . . Q: Why does a giraffe have such a long neck? . . . . . . . . . . A: Because it is so far from its head to its body.
  6. Papa_Bear1

    #Name? Showing on one form, but not the other -

    I'm just glad it was easy and hopefully I updated it fast enough so that I didn't waste anyone's time.... good grief...
  7. Papa_Bear1

    #Name? Showing on one form, but not the other -

    Sorry - I posted too soon ---- I figured it out. It was because I had code in the Load event that updated the recordsource to a DIFFERENT query - but only in that one form. Oops. So never mind... ;)
  8. Papa_Bear1

    #Name? Showing on one form, but not the other -

    I have two forms, both of which I've updated the data source to a new query - and both are presenting the exact same new field from that exact same query... One form works fine, the other shows "#Name?". I've double-checked the field name is correct. The two forms are both of the same type -...
  9. Papa_Bear1

    Hi!

    Indeed ---- ;-) I just ran into a problem - we'll see if I can figure out where/how to post it...
  10. Papa_Bear1

    Hi!

    @pbaldy, @isladogs— yes, it worked... good to know... thanks!
  11. Papa_Bear1

    Hi!

    Thanks all! So - dumb question - do you use the "@" prefix to refer to usernames - or is that not used here?
  12. Papa_Bear1

    Query Help with date and comments

    Here's a possibility - maybe: Query 1 (qryTest1) written as such: SELECT T.[Partners Name] AS Partners, Max(T.[Comment Date]) AS Comment_Date FROM [Any Table] AS T GROUP BY T.[Partners Name]; With Query 2 written to use qryTest1 - to give your intended outcome: SELECT Q.Partners...
  13. Papa_Bear1

    Solved IF with Record count

    theDBguy is spot on... I will often do a dim strSQL as String, and then set that variable to the string that defines the query. You would then have ...OpenRecordset(strSQL) instead. I would then pause the code at that point, use the "View Immediate" screen, and type ?strSQL in it - to grab...
  14. Papa_Bear1

    Hi!

    Thanks - looking forward to starting here (rather than Google) for my occasional Access questions... should be interesting.
  15. Papa_Bear1

    Hi!

    I'm Papa_Bear1 and I'm just introducing myself to AccessWorld. I've been programming in Access since I can remember (... the early 90s... ;-) I think it is a fantastic realm to live in. I've been singing the praises of MS Access for many years. I do admit that having used it for so long, I...
Back
Top Bottom