Search results

OK I've solved the problem, but I have another question: Querying a multivalue field. A have a query that selects the multivalue field. The query forms the record source for a subform. The text values in the multivalue field are displayed in the query, but when I save this and view the data...

Bumping for replies. What's the problem with multivalue fields in your opinions?

Ah OK thanks. I understand now. That's the article I started from. So do you use Junction tables instead of multivalue fields? I've heard the principle is the same, with a multivalue field just creating a junction table "behind the scenes." What's the major problems with multivalue fields?

No they're a supported feature. You can have a field that contains multiple values.

I have a multivalue field containing values of A,B,C and D with primary IDs of 1,2,3 and 4 in that order. If I was to run: UPDATE Table Set Table.Multivalue.Value = 1 WHERE Field 1 = "True" AND Field 2 = "True"; Then run UPDATE Table Set Table.Multivalue.Value = 2 WHERE Field 1 = "True" AND...

Dim DateValue As Date DateValue = DateBox.Value Dim DateCheck As Boolean DateCheck = IsDate(DateValue) Dim DateBox_Parameter As String If DateCheck = "True" Then STATEMENT Else STATEMENT End If

It refuses to even let me enter that date. It just changes it automatically to 01/01/2001, which is no good. Is there any way I can reference "default" as a value without putting in the actual default value in this case?

Doesn't work I'm afraid. "Invalid Use of Null" The only think i can think of is to use the default text box date value which is 01/01/0001 which would be very unlikely to be queried anyway. I'll try that.

Ah OK... From http://msdn.microsoft.com/en-us/library/office/gg264241.aspx If I was to change the default value to "null" in the property sheet, this wouldn't be seen as a date value and would represent the condition of the text box being blank? I'll try it.

Hi again I have a text box with a date picker in a form. I need to create a piece of conditional logic in Visual Basic that is activated when the value in the form is not null. I can't so this in the same way as I would with a string which would be: If Field <> "" Then Statement End If Does...

GODAMMIT I just figured it out. It's not "Else If" it's "ElseIf" I'll stop being such a newb someday I promise.

OK, so I got my code working but now I've hit another snag. As mentioned, I'm using SQL to create a dynamic SQL query. So something like: SELECT * WHERE (FieldA = 1 OR FieldA = 2) AND (FieldB = 1 OR FieldB = 2); I'm now coding the AND (FieldB = 1 OR FieldB = 2) FYI Each of the Field values...

I changed the way I was adding variables into the SQL string similar to the way you said, then I changed the position of the first Dims to be in the same Sub routine as the main code, finally I found that one of my SQL variables was incorrect for my database. Huge relief. That was the last...

Figured it out. Thanks for pointing me in the right direction.

OK so Record_Source = "SELECT * FROM Query WHERE " & AdultParameter & FamilyParameter & FounderParameter & WatchParameter & BusinessParameter & ";" But if I do this, I get an end of statement error. Is it a different type of quotation mark/enclosing symbol other than "" used? Yes lol. It's a...

Still not recognizing a value for the parameters.

Dim Check1Value As Boolean Dim Check2Value As Boolean Private Sub Check1_Click() Check1Value = Check1.Value End Sub Private Sub Check2_Click() Check2Value = Check2.Value End Sub Like this?

Ah, so they need to start with Public Sub Check1_Click()?

I've attempted to create a form with a dynamic subform. Records for the subform are filtered using check boxes which supplies parameters to the Visual Basic script (below). The VB Script changes the Record Source (SQL) of the subform. Checkbox variables are defined/declared: Private Sub...

Putting '' around a value makes Access think it's a text value?