By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,851 Members | 1,183 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,851 IT Pros & Developers. It's quick & easy.

Selecting Specific Records In A Multiuser Database

P: n/a
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!
Mar 10 '08 #1
Share this Question
Share on Google+
3 Replies


P: n/a
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 myLocalSelectTable)

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:

http://www.mvps.org/access/api/api0008.htm

And, the current computer name with:

http://www.mvps.org/access/api/api0009.htm

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
pl*****************@msn.com
Mar 11 '08 #2

P: n/a
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" <Pl*******************@msn.comwrote in message
news:3%jBj.69561$pM4.61006@pd7urf1no...
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 myLocalSelectTable)

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:

http://www.mvps.org/access/api/api0008.htm

And, the current computer name with:

http://www.mvps.org/access/api/api0009.htm

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
pl*****************@msn.com


Mar 12 '08 #3

P: n/a

"Steve" <Em***@Invalid.comschreef in bericht news:13*************@corp.supernews.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
Mar 12 '08 #4

This discussion thread is closed

Replies have been disabled for this discussion.