Selecting Specific Records In A Multiuser Database

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Steve

    Selecting Specific Records In A Multiuser Database

    Say a multiuser database has over five hundred customers and I want to be
    able to send email to selected customers. What is the standard way to select
    the customers? At first I thought of just havung a Yes/No field in the
    customers field but then thought my selections might interfere with the
    seletions of other users and vice versa.

    Thanks!


  • Albert D. Kallal

    #2
    Re: Selecting Specific Records In A Multiuser Database

    There is two approaches I often use:


    1) add two fields MailSelect + UserName

    so, when user clicks on the MailSelect field, you automatic place the
    current logged on users name into the Username field.


    2) You create a table that is local to your front end, and simply insert the
    ID's into that local table.

    Then, to select, you go

    select * from tblcustomers where ID in (select id from myLocalSelectTa ble)

    Note that these "where" clauses that are sub-selects even work as a "where"
    clause for reprots.

    Approach #2 might not work if you need others to be able to print, or use
    that list you made from different workstations.

    You can get the current network logon name with:



    And, the current computer name with:



    And, if using ms-access security, then currentuser() will return the
    ms-access logon.

    I often log all 3 of the above values in some applications.


    --
    Albert D. Kallal (Access MVP)
    Edmonton, Alberta Canada
    pleaseNOOSpamKa llal@msn.com


    Comment

    • Steve

      #3
      Re: Selecting Specific Records In A Multiuser Database

      Thanks for responding, Albert!

      In approach#1, if another user clicks on the MailSelect field of a customer
      you selected while you are making your selections, you lose your selected
      customer. That's what my question is about!

      Thanks!



      "Albert D. Kallal" <PleaseNOOOsPAM mkallal@msn.com wrote in message
      news:3%jBj.6956 1$pM4.61006@pd7 urf1no...
      There is two approaches I often use:
      >
      >
      1) add two fields MailSelect + UserName
      >
      so, when user clicks on the MailSelect field, you automatic place the
      current logged on users name into the Username field.
      >
      >
      2) You create a table that is local to your front end, and simply insert
      the ID's into that local table.
      >
      Then, to select, you go
      >
      select * from tblcustomers where ID in (select id from myLocalSelectTa ble)
      >
      Note that these "where" clauses that are sub-selects even work as a
      "where" clause for reprots.
      >
      Approach #2 might not work if you need others to be able to print, or use
      that list you made from different workstations.
      >
      You can get the current network logon name with:
      >

      >
      And, the current computer name with:
      >

      >
      And, if using ms-access security, then currentuser() will return the
      ms-access logon.
      >
      I often log all 3 of the above values in some applications.
      >
      >
      --
      Albert D. Kallal (Access MVP)
      Edmonton, Alberta Canada
      pleaseNOOSpamKa llal@msn.com
      >
      >

      Comment

      • Arno R

        #4
        Re: Selecting Specific Records In A Multiuser Database


        "Steve" <Email@Invalid. comschreef in bericht news:13tee2v9t0 e3odf@corp.supe rnews.com...
        Thanks for responding, Albert!

        In approach#1, if another user clicks on the MailSelect field of a customer
        you selected while you are making your selections, you lose your selected
        customer. That's what my question is about!
        Simply use a local temptable for the mailselect.
        If bloat is an issue then put the temptable(s) in a separate app_tmp.mdb that is created every time you start the app.

        Arno R

        Comment

        Working...