Tools2
  Home FAQ Contact Sign in
 
Advanced search
MATCHING GROUPS



more...
POPULAR GROUPS

more...

found 7 articles for 0.302 sec
Thanks a lot Dave, Your help is highly appreciated. I have also found a sample database to do what I need to do at http://www.rogersaccesslibrary.com/download3.asp?SampleName=CreateMultiSelectQuery.mdb Have a nice day! GeorgeCY Ο χρήστης "Klatuu" έγγραψε: > The code I posted will create a string that can be used as a Where clause for > a query, but without the word WHERE. >     

Group: microsoft.public.access.forms · Group Profile · Search for Tools2 in microsoft.public.access.forms
Author: George
Date: May 28, 2007 02:07

The code I posted will create a string that can be used as a Where clause for a query, but without the word WHERE. I would suggest a command button to run the query or queries you need. To call the function, you pass it the control object. strWhere = BuildWhere(Me.List1) Now, how you construct the query can be done a number of ways. You could do it all in VBA: strSQL = "SELECT
Show full article (5.07Kb)
My friend, thanks a lot for your answer, Sorry, but i got a bit confused. I am a newbie in coding. I have already created on my form a list box (list1) which shows all different categories (grouped) from a query. What shall I do next? I need to have multiple selctions from this list and then to run a second query to match (from my table) all related records. Thanks again, GeorgeCY     

Group: microsoft.public.access.forms · Group Profile · Search for Tools2 in microsoft.public.access.forms
Author: Klatuu
Date: May 26, 2007 14:06

If you need to make multiple selections from your category list, you probably need a multi select list box rather than a combo box. It takes a bit more code, but will allow you to do this. To determine which categories the user has selected, you will need to use the ItemsSelected collection of the list box to find which are selected. Here is an example from one of my applications. It builds
Show full article (4.54Kb)
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install     

Group: microsoft.public.access.forms · Group Profile · Search for Tools2 in microsoft.public.access.forms
Author: George
Date: May 26, 2007 01:14

As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install
Show full article (2.74Kb) · Show article thread
As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically schedule removal of ports that have been judged to have outlived their usefulness. Often, this is due to a better alternative having become available and/or the cessation of development on the existing port. In some cases, ports are marked for removal because they fail to build and install     

Group: microsoft.public.access.forms · Group Profile · Search for Tools2 in microsoft.public.access.forms
Author: Klatuu
Date: May 25, 2007 06:13

Show full article (2.18Kb)
    

Group: muc.lists.freebsd.ports · Group Profile · Search for Tools2 in muc.lists.freebsd.ports
Author: linimon
Date: Jan 29, 2007 23:51

Show full article (45.87Kb)
    

Group: muc.lists.freebsd.ports · Group Profile · Search for Tools2 in muc.lists.freebsd.ports
Author: linimon
Date: Nov 22, 2006 10:56

Show full article (57.24Kb)
    

Group: muc.lists.freebsd.ports · Group Profile · Search for Tools2 in muc.lists.freebsd.ports
Author: linimon
Date: Sep 29, 2006 12:40

Show full article (81.33Kb)