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

Filtering with multiple possible search values.

blyxx86
100+
P: 256
I am trying to filter multiple entries with only one search box. That way the user can type whatever they want and find all the values that contain what they enter.

Expand|Select|Wrap|Line Numbers
  1. Private Sub txtLookup_AfterUpdate()
  2. Me.Filter = "[Serial] Like '*" & [txtLookup] & "*'" OR "[Technician] Like '*" & [txtLookup] & "*'"
  3. Me.FilterOn = True
  4. End Sub
  5.  
It allows for variables and to filter within the form. I can't seem to find a way to make it actually search through multiple fields (Serial, Technician, Date, etc..)

The above code works fine if I do just one at a time
Expand|Select|Wrap|Line Numbers
  1. Private Sub txtLookup_AfterUpdate()
  2. Me.Filter = "[Serial] Like '*" & [txtLookup] & "*'" 
  3. Me.FilterOn = True
  4. End Sub
  5.  
I could do a filter for each lookup, but would prefer it all in one place. I'm new to VBA, so I don't really know how to include multiple values after Me.Filter = ... I tried mimicking the values from a SQL search, but that didn't seem to work either.
Nov 28 '06 #1
Share this Question
Share on Google+
23 Replies


NeoPa
Expert Mod 15k+
P: 31,661
The SQL search parameters are exactly what you need.
Lose the 'WHERE ' part though.
Nov 28 '06 #2

blyxx86
100+
P: 256
The SQL search parameters are exactly what you need.
Lose the 'WHERE ' part though.
Copy and paste exactly? Lots of parenthesis in the SQL statement. I didn't think VBA 'did' parenthesis.
Nov 28 '06 #3

blyxx86
100+
P: 256
Copy and paste exactly? Lots of parenthesis in the SQL statement. I didn't think VBA 'did' parenthesis.
Expand|Select|Wrap|Line Numbers
  1. Me.Filter = (([Serial] Like "*" & [txtLookup] & "*") Or ([Customer] Like "*" & [txtLookup] & "*") Or ([Technician] Like "*" & [txtLookup] & "*") Or ([Model] Like "*" & [txtLookup] & "*") Or ([Technician] Like "*" & [txtLookup] & "*"))
  2.  
tried with them being in parenthesis and with brackets. Both ways returned an:
"Invalid use of null" Run-time error '94'
Nov 28 '06 #4

MMcCarthy
Expert Mod 10K+
P: 14,534
Expand|Select|Wrap|Line Numbers
  1. Me.Filter = (([Serial] Like "*" & [txtLookup] & "*") Or ([Customer] Like "*" & [txtLookup] & "*") Or ([Technician] Like "*" & [txtLookup] & "*") Or ([Model] Like "*" & [txtLookup] & "*") Or ([Technician] Like "*" & [txtLookup] & "*"))
  2.  
tried with them being in parenthesis and with brackets. Both ways returned an:
"Invalid use of null" Run-time error '94'
You must place the full statement in a string and break the string to allow the textbox value to be assigned. You will need single quotes around all your textbox values as follows:

Expand|Select|Wrap|Line Numbers
  1.  
  2. Me.Filter = "(([Serial] Like '*" & [txtLookup] & "*') Or ([Customer] Like '*" & [txtLookup] & "*') Or ([Technician] Like '*" & [txtLookup] & "*') Or ([Model] Like '*" & [txtLookup] & "*') Or ([Technician] Like '*" & [txtLookup] & "*'))"
  3.  
Does this solve the problem?

Also does your current record source have a where statement already? If the answer is yes then you will need to add " AND (([Serial]......"
Nov 28 '06 #5

NeoPa
Expert Mod 15k+
P: 31,661
Also does your current record source have a where statement already? If the answer is yes then you will need to add " AND (([Serial]......"
I don't think that's quite right.
The filter is applied over and above the existing query. A bit like a sub-query.
If you already have a Filter set, however, and you still need it then you may need to incorporate this into your new string. The exact logic you would be after, would determine whether to AND or OR, and how to parenthesise.

PS. Performance will likely suffer if you have all these filter parts.
If you have a number of filter parts you should consider applying only those with contents (in other words drop any mention of a filter part that has not been selected by the operator). This would need to be organised in the VBA.
Nov 28 '06 #6

MMcCarthy
Expert Mod 10K+
P: 14,534
I don't think that's quite right.
The filter is applied over and above the existing query. A bit like a sub-query.
If you already have a Filter set, however, and you still need it then you may need to incorporate this into your new string. The exact logic you would be after, would determine whether to AND or OR, and how to parenthesise.

PS. Performance will likely suffer if you have all these filter parts.
If you have a number of filter parts you should consider applying only those with contents (in other words drop any mention of a filter part that has not been selected by the operator). This would need to be organised in the VBA.
Are you daring to argue with me again? :D

I was just trying to cover all bases, I'd guess that the string syntax will fix the problem.

Mary
Nov 28 '06 #7

blyxx86
100+
P: 256
I don't think that's quite right.
The filter is applied over and above the existing query. A bit like a sub-query.
If you already have a Filter set, however, and you still need it then you may need to incorporate this into your new string. The exact logic you would be after, would determine whether to AND or OR, and how to parenthesise.

PS. Performance will likely suffer if you have all these filter parts.
If you have a number of filter parts you should consider applying only those with contents (in other words drop any mention of a filter part that has not been selected by the operator). This would need to be organised in the VBA.
I did notice a difference in performance, and do believe it will be best to just have a form of list boxes, select the desirable Technician/Customer/Etc.. and display the list in that manner. Instead of searching for random strings. However, searching by serial is definitely needed.

On a sidenote. I have a text box that I am now trying to input it's value into the main table. The control source for the text box is...

Expand|Select|Wrap|Line Numbers
  1. =IIf(([cboScanner]="Pass" And [cboDisplay]="Pass" And [cboKeypad]="Pass" And [cboRadio]="Pass" And [cboStructural]="Pass"),"Pass","Fail")
It is used to determine that all the fields are "Pass" otherwise it will return "Fail". It's an all or nothing deal. Now I can't seem to input this value into the table. I've tried making the value of another box that is bound to the column "overall" in the main table, but it doesn't seem to input anything.

I had something LIKE this:
Expand|Select|Wrap|Line Numbers
  1. Private Sub txtOverall_AfterUpdate()
  2. Const cQuote = """"  'Thats two quotes
  3.     Me!txtOverall.Value = cQuote & Me!cboOverall.Value & cQuote
  4. End Sub
  5.  
This did nothing. I tried it in the BeforeUpdate as well. No luck. It left the box blank.

And to think one month ago, I knew absolutely NOTHING of databases. Never used one before either. Never did any coding (except "Basic") and now look at me, writing some things on my own. :) still needing help though, so I can't be too good. Never any time to really sit down and fiddle though, and I really like fiddling.
Nov 28 '06 #8

blyxx86
100+
P: 256
I did notice a difference in performance, and do believe it will be best to just have a form of list boxes, select the desirable Technician/Customer/Etc.. and display the list in that manner. Instead of searching for random strings. However, searching by serial is definitely needed.

On a sidenote. I have a text box that I am now trying to input it's value into the main table. The control source for the text box is...

Expand|Select|Wrap|Line Numbers
  1. =IIf(([cboScanner]="Pass" And [cboDisplay]="Pass" And [cboKeypad]="Pass" And [cboRadio]="Pass" And [cboStructural]="Pass"),"Pass","Fail")
It is used to determine that all the fields are "Pass" otherwise it will return "Fail". It's an all or nothing deal. Now I can't seem to input this value into the table. I've tried making the value of another box that is bound to the column "overall" in the main table, but it doesn't seem to input anything.

I had something LIKE this:
Expand|Select|Wrap|Line Numbers
  1. Private Sub txtOverall_AfterUpdate()
  2. Const cQuote = """"  'Thats two quotes
  3.     Me!txtOverall.Value = cQuote & Me!cboOverall.Value & cQuote
  4. End Sub
  5.  
This did nothing. I tried it in the BeforeUpdate as well. No luck. It left the box blank.

And to think one month ago, I knew absolutely NOTHING of databases. Never used one before either. Never did any coding (except "Basic") and now look at me, writing some things on my own. :) still needing help though, so I can't be too good. Never any time to really sit down and fiddle though, and I really like fiddling.
Oooh, epiphany...

Would I do something like this, instead???

Expand|Select|Wrap|Line Numbers
  1. DoCmd.RunSQL = INSERT INTO .....  blah blah blah.
  2.  
Would this be on a beforeupdate, or afterupdate?
Nov 28 '06 #9

NeoPa
Expert Mod 15k+
P: 31,661
My brain is currently fried, but even I can see interesting things happening here.
I've set a reminder to check this thread again tomorrow.

In the mean time a couple of simple points :
RunSQL needs a string "INSERT INTO ...".
Expand|Select|Wrap|Line Numbers
  1. Const cQuote = """"  'Thats two quotes (No it's not it's just the one)
Always use single quotes (') for strings within SQL (not building up the string - just what gets passed to SQL).
Expand|Select|Wrap|Line Numbers
  1. =IIf(([cboScanner]="Pass" And [cboDisplay]="Pass" And [cboKeypad]="Pass" And [cboRadio]="Pass" And [cboStructural]="Pass"),"Pass","Fail") can be rewritten as :
  2. =IIf([cboScanner] & [cboDisplay] & [cboKeypad] & [cboRadio] & [cboStructural]="PassPassPassPassPass","Pass","Fail")
Boolean values are easier to deal with still.

I'll revisit tomorrow.
Nov 29 '06 #10

blyxx86
100+
P: 256
My brain is currently fried, but even I can see interesting things happening here.
I've set a reminder to check this thread again tomorrow.

In the mean time a couple of simple points :
RunSQL needs a string "INSERT INTO ...".
Expand|Select|Wrap|Line Numbers
  1. Const cQuote = """"  'Thats two quotes (No it's not it's just the one)
Always use single quotes (') for strings within SQL (not building up the string - just what gets passed to SQL).
Expand|Select|Wrap|Line Numbers
  1. =IIf(([cboScanner]="Pass" And [cboDisplay]="Pass" And [cboKeypad]="Pass" And [cboRadio]="Pass" And [cboStructural]="Pass"),"Pass","Fail") can be rewritten as :
  2. =IIf([cboScanner] & [cboDisplay] & [cboKeypad] & [cboRadio] & [cboStructural]="PassPassPassPassPass","Pass","Fail")
Boolean values are easier to deal with still.

I'll revisit tomorrow.
I don't like how sometimes you put spaces and commas, and sometimes you don't. It's confusing to me.

SO something like this is what I'm looking for?
Expand|Select|Wrap|Line Numbers
  1. Dim strSQL As String
  2. strSQL = "INSERT INTO tblQC(Overall) Values([txtOverall])"
  3. DoCmd.RunSQL (strSQL)
  4. End Sub
  5.  
That worked, but doesn't do what I wanted it to.. it appends a new row. I'd like to include it on my current record that I am working on within the form..

This is so frustrating.

I dont understand SQL and how it's all related within the database.
Nov 29 '06 #11

MMcCarthy
Expert Mod 10K+
P: 14,534
I don't like how sometimes you put spaces and commas, and sometimes you don't. It's confusing to me.

SO something like this is what I'm looking for?
Expand|Select|Wrap|Line Numbers
  1. Dim strSQL As String
  2. strSQL = "INSERT INTO tblQC(Overall) Values([txtOverall])"
  3. DoCmd.RunSQL (strSQL)
  4. End Sub
  5.  
That worked, but doesn't do what I wanted it to.. it appends a new row. I'd like to include it on my current record that I am working on within the form..

This is so frustrating.

I dont understand SQL and how it's all related within the database.
You can use an UPDATE command but you will have to set criteria in the WHERE to identify which record you want updated.

Expand|Select|Wrap|Line Numbers
  1.  
  2. strSQL = "UPDATE tblQC SET Overall='" & [txtOverall] & "' WHERE .....;"
  3.  
Nov 29 '06 #12

blyxx86
100+
P: 256
You can use an UPDATE command but you will have to set criteria in the WHERE to identify which record you want updated.

Expand|Select|Wrap|Line Numbers
  1.  
  2. strSQL = "UPDATE tblQC SET Overall='" & [txtOverall] & "' WHERE .....;"
  3.  
I tried doing that at home yesterday on a mock database. I had the WHERE clause..

WHERE ID = [txtID]

ID is a primary key on my table, and txtID is the field on my form.

it didn't update the records. I'm gonna try to learn a bit more SQL, because I see how much it is used. Not to mention it's a good thing to know.

I will go over to the SQL forum and see if what types of help I can get there as well to expand my knowledge. As I've said before, I've only been doing this (on a small amount of time) for a little over a month, so i'm surprised I've gotten as far as I have.

Also, I'm thinking of redoing the entire database once I learn everything I think I need to know and streamline the process.
Nov 29 '06 #13

MMcCarthy
Expert Mod 10K+
P: 14,534
Try ...

Expand|Select|Wrap|Line Numbers
  1. strSQL = "UPDATE tblQC SET Overall='" & [txtOverall] & "' WHERE ID =" & [txtID] & ";"
  2.  
I tried doing that at home yesterday on a mock database. I had the WHERE clause..

WHERE ID = [txtID]

ID is a primary key on my table, and txtID is the field on my form.

it didn't update the records. I'm gonna try to learn a bit more SQL, because I see how much it is used. Not to mention it's a good thing to know.

I will go over to the SQL forum and see if what types of help I can get there as well to expand my knowledge. As I've said before, I've only been doing this (on a small amount of time) for a little over a month, so i'm surprised I've gotten as far as I have.

Also, I'm thinking of redoing the entire database once I learn everything I think I need to know and streamline the process.
Nov 29 '06 #14

blyxx86
100+
P: 256
Try ...

Expand|Select|Wrap|Line Numbers
  1. strSQL = "UPDATE tblQC SET Overall='" & [txtOverall] & "' WHERE ID =" & [txtID] & ";"
  2.  
Any good links on SQL and VBA? I looked at the links you've posted, but not the greatest amount of information for basic information. However, I did like the link of security controls. Going to need those soon.

Just some basic SQL

Why did you put " & [control] & " around the things. What is the function of the ampersand? How do I know when to use " and when to use ' ?
Nov 29 '06 #15

blyxx86
100+
P: 256
Any good links on SQL and VBA? I looked at the links you've posted, but not the greatest amount of information for basic information. However, I did like the link of security controls. Going to need those soon.

Just some basic SQL

Why did you put " & [control] & " around the things. What is the function of the ampersand? How do I know when to use " and when to use ' ?
Nope, didn't work.

I renamed the fields and such to match the ones on my form (was at home when I wrote that one)..

Expand|Select|Wrap|Line Numbers
  1. Private Sub cboOverall_AfterUpdate()
  2. Dim strSQL As String
  3. strSQL = "UPDATE QC SET Overall='" & [cboOverall] & "' WHERE ID =" & [ID] & ";"
  4. DoCmd.RunSQL (strSQL)
  5.  
  6. End Sub
  7.  
I'd really like this field to be automatically adjusted based on the values of the other fields. I was able to do it in excel and transfer it to a database as a value, of course using the wizard, so I'm not sure why it's not letting us do this now. Do I need to put the field names on the form to reference their relative position? Does it maybe not know where to get the information from?

Ok, so recap...
The control source of cboOverall (haven't dont the boolean values like suggested just because i don't really know them yet)
Expand|Select|Wrap|Line Numbers
  1. =IIf(([cboScanner]="Pass" And [cboDisplay]="Pass" And [cboKeypad]="Pass" And [cboRadio]="Pass" And [cboStructural]="Pass"),"Pass","Fail")
  2.  
My table has the field: Overall
I am trying to input the value from cboOverall into the table QC and the field Overall via the code:
Expand|Select|Wrap|Line Numbers
  1. Private Sub cboOverall_AfterUpdate()
  2. Dim strSQL As String
  3. strSQL = "UPDATE QC SET Overall='" & [cboOverall] & "' WHERE ID =" & [ID] & ";"
  4. DoCmd.RunSQL (strSQL)
  5.  
  6. End Sub
  7.  
What's going wrong?
Nov 29 '06 #16

MMcCarthy
Expert Mod 10K+
P: 14,534
Nope, didn't work.

I renamed the fields and such to match the ones on my form (was at home when I wrote that one)..

Expand|Select|Wrap|Line Numbers
  1. Private Sub cboOverall_AfterUpdate()
  2. Dim strSQL As String
  3. strSQL = "UPDATE QC SET Overall='" & [cboOverall] & "' WHERE ID =" & [ID] & ";"
  4. DoCmd.RunSQL (strSQL)
  5.  
  6. End Sub
  7.  
The values in the square brackets surrounded by ampersands are the controls on the form and should be named accordingly. Values that contain text should also be surrounded by single quotes and values that contain dates should also be surrounded by # characters.

The following site from the links is a good starting site for anyone.

Tutorials and General Help

This site has something for both the beginner and the advanced user. It provides tutorials, general how-to's on everything from table structure, to VBA. It also has a page which covers all commonly used functions.

http://www.techonthenet.com/access/index.php
Nov 29 '06 #17

NeoPa
Expert Mod 15k+
P: 31,661
I seem to have missed a whole conversation here :s.
I'll try to address each point clearly and in order.
I don't like how sometimes you put spaces and commas, and sometimes you don't. It's confusing to me.
I don't understand what your referring to in your statement (question?).
I can normally explain why I do things in any particular way though, so if you want clarification, just ask.
WHERE ID = [txtID]
As the SQL code is executed by an 'engine' which in unrelated to your form, you will need to provide an absolute reference to it OR add it into the string before execution.
Expand|Select|Wrap|Line Numbers
  1. strSQL = "... WHERE [ID] = Forms![YourFormName].[txtID]"
  2. OR
  3. strSQL = "... WHERE [ID] = " & [txtID]
(Will explain '&' later.)
I will go over to the SQL forum and see if what types of help I can get there as well to expand my knowledge.
There is no SQL forum, as such. Understandable mistake though. SQL Server & MySQL are both servers that process SQL.
The best place to ask questions about the SQL you would use in Access is in here.
Why did you put " & [control] & " around the things. What is the function of the ampersand? How do I know when to use " and when to use ' ?
Ampersand (&) is a string concatenation command in VBA.
So,
Expand|Select|Wrap|Line Numbers
  1. strSQL = "SELECT * " & "FROM [Table]"
  2. Debug.Print strSQL
What you will see printed is :
SELECT * FROM [Table]
Engines (or processes which interpret your code and SQL) must have a way of determining the type of any code you enter.
Putting quotes around a string tells the compiler or SQL engine that the enclosed characters should be treated as string literals.
The VBA copiler recognises double-quotes as string delimiters only. So "The Quick ..." is a string but 'The Quick ...' is not.
The Access SQL interpreter or engine recognises both single- (') and double-quotes (") but the standard character for SQL generally is the single-quote.
For this reason, and because it makes life a lot easier when working with both together, I always advise using the standard single-quote for strings within SQL.
The underscore (_) is a VBA char that tells the compiler to treat the following line as a continuation of the current btw.
Expand|Select|Wrap|Line Numbers
  1. strSQL = "SELECT * " & _
  2.     "FROM [MyTable] " & _
  3.     "WHERE ([NameField]='Richard')"
Notice that Richard, which is passed to the SQL engine, is in (') whereas all the others, which are not passed because they are interpreted by VBA first, are in (").
What is actually passed on to SQL is :
SELECT * FROM [MyTable] WHERE ([NameField]='Richard')
Nov 29 '06 #18

blyxx86
100+
P: 256
I seem to have missed a whole conversation here :s.
I'll try to address each point clearly and in order.

I don't understand what your referring to in your statement (question?).
I can normally explain why I do things in any particular way though, so if you want clarification, just ask.

As the SQL code is executed by an 'engine' which in unrelated to your form, you will need to provide an absolute reference to it OR add it into the string before execution.
Expand|Select|Wrap|Line Numbers
  1. strSQL = "... WHERE [ID] = Forms![YourFormName].[txtID]"
  2. OR
  3. strSQL = "... WHERE [ID] = " & [txtID]
(Will explain '&' later.)

There is no SQL forum, as such. Understandable mistake though. SQL Server & MySQL are both servers that process SQL.
The best place to ask questions about the SQL you would use in Access is in here.

Ampersand (&) is a string concatenation command in VBA.
So,
Expand|Select|Wrap|Line Numbers
  1. strSQL = "SELECT * " & "FROM [Table]"
  2. Debug.Print strSQL
What you will see printed is :
SELECT * FROM [Table]
Engines (or processes which interpret your code and SQL) must have a way of determining the type of any code you enter.
Putting quotes around a string tells the compiler or SQL engine that the enclosed characters should be treated as string literals.
The VBA copiler recognises double-quotes as string delimiters only. So "The Quick ..." is a string but 'The Quick ...' is not.
The Access SQL interpreter or engine recognises both single- (') and double-quotes (") but the standard character for SQL generally is the single-quote.
For this reason, and because it makes life a lot easier when working with both together, I always advise using the standard single-quote for strings within SQL.
The underscore (_) is a VBA char that tells the compiler to treat the following line as a continuation of the current btw.
Expand|Select|Wrap|Line Numbers
  1. strSQL = "SELECT * " & _
  2.     "FROM [MyTable] " & _
  3.     "WHERE ([NameField]='Richard')"
Notice that Richard, which is passed to the SQL engine, is in (') whereas all the others, which are not passed because they are interpreted by VBA first, are in (").
What is actually passed on to SQL is :
So an (&) is basically what tells the engine that the next string is part of the code as well.. because if you write just SELECT FROM the engine would try to run the command as "SELECT * FROM" and not, "SELECT *" "FROM"

I still don't know why my code won't work though.
Nov 29 '06 #19

blyxx86
100+
P: 256
I seem to have missed a whole conversation here :s.
I'll try to address each point clearly and in order.

I don't understand what your referring to in your statement (question?).
I can normally explain why I do things in any particular way though, so if you want clarification, just ask.

As the SQL code is executed by an 'engine' which in unrelated to your form, you will need to provide an absolute reference to it OR add it into the string before execution.
Expand|Select|Wrap|Line Numbers
  1. strSQL = "... WHERE [ID] = Forms![YourFormName].[txtID]"
  2. OR
  3. strSQL = "... WHERE [ID] = " & [txtID]
(Will explain '&' later.)

There is no SQL forum, as such. Understandable mistake though. SQL Server & MySQL are both servers that process SQL.
The best place to ask questions about the SQL you would use in Access is in here.

Ampersand (&) is a string concatenation command in VBA.
So,
Expand|Select|Wrap|Line Numbers
  1. strSQL = "SELECT * " & "FROM [Table]"
  2. Debug.Print strSQL
What you will see printed is :
SELECT * FROM [Table]
Engines (or processes which interpret your code and SQL) must have a way of determining the type of any code you enter.
Putting quotes around a string tells the compiler or SQL engine that the enclosed characters should be treated as string literals.
The VBA copiler recognises double-quotes as string delimiters only. So "The Quick ..." is a string but 'The Quick ...' is not.
The Access SQL interpreter or engine recognises both single- (') and double-quotes (") but the standard character for SQL generally is the single-quote.
For this reason, and because it makes life a lot easier when working with both together, I always advise using the standard single-quote for strings within SQL.
The underscore (_) is a VBA char that tells the compiler to treat the following line as a continuation of the current btw.
Expand|Select|Wrap|Line Numbers
  1. strSQL = "SELECT * " & _
  2.     "FROM [MyTable] " & _
  3.     "WHERE ([NameField]='Richard')"
Notice that Richard, which is passed to the SQL engine, is in (') whereas all the others, which are not passed because they are interpreted by VBA first, are in (").
What is actually passed on to SQL is :
This is the thing I was confused about:
Expand|Select|Wrap|Line Numbers
  1. =IIf([cboScanner] & [cboDisplay] & [cboKeypad] & [cboRadio] & [cboStructural]="PassPassPassPassPass","Pass","Fail")
  2.  
Wouldn't the engine recognize "PassPassPassPassPass" as one string? How does it differentitate between "'Pass' & 'Pass' & 'Pass' & 'Pass' & 'Pass'" wouldn't that make more sense to tie into what you just said about the ampersand and single quotations?
Nov 29 '06 #20

NeoPa
Expert Mod 15k+
P: 31,661
Good question, but the answer's No.
Check out the string it's comparing it to.
If ALL the individual values are "Pass", then the concatenated string will be "PassPassPassPass".
Nov 29 '06 #21

blyxx86
100+
P: 256
Good question, but the answer's No.
Check out the string it's comparing it to.
If ALL the individual values are "Pass", then the concatenated string will be "PassPassPassPass".
I get it now, that makes sense actually. It's looking for the value of them all together. Since you put no spaces between them, it comes out looking like "PassPassPass......" That makes sense, but I won't really understand the use of that for a while.

If you have any ideas to my other problem, I started a new discussion titled.. "I'm Stuck! - ....."
Nov 30 '06 #22

NeoPa
Expert Mod 15k+
P: 31,661
I'm sure I'll get to it in time, but I'm struggling to keep up with all the new posts and threads atm.
Nov 30 '06 #23

blyxx86
100+
P: 256
I'm sure I'll get to it in time, but I'm struggling to keep up with all the new posts and threads atm.
MMcCarthy helped me figure it out, thank you though!
Nov 30 '06 #24

Post your reply

Sign in to post your reply or Sign up for a free account.