Search results

Just guessing, but try reversing these two lines. If you set the SQL of a query, I would expect this automatically invalidates its previous parameters collection.

When you build a house you do not build a kitchen under one roof, and a bedroom under a different roof, and a bathroom under still another. To make living your life easier, you build one roof, and you build all the rooms of your house very closely connected. Apply this thinking to your...

.

Maybe elaborate on this.

I don't see why you even need a subquery. Does this query work with your data? SELECT tv.Centre_ID, Max(tv.Date_visited) AS MaxOfDate_visited, tc.[Centre Name], tc.Suburb, tc.Region FROM t_Centres As tc INNER JOIN t_Visits As tv ON tc.ID = tv.Centre_ID GROUP BY tv.Centre_ID, tc.[Centre Name]...

Things that help: 1) indicate what line causes the error. 2) use code tags. Code is hard to understand, especially other people's code. Preserving your indents and structure helps a lot. 3) post all the code. hth

If what matters to your goal is attendance, not absence, then only track attendance. If there is no attendance record, the student did not attend. To query this data, use an outer join. If the linked table row ID is null, a row does not exist, and, depending on what angle you came at it from...

I would not record both presence AND absence. It is a boolean value, and therefore impossible in the real world that both might exist. Thus, make it impossible in your model as follows-->assume one, and record the other. Create a tAbsent table that stores PK, StudentFK and Date, and you are...

Everything?

Yeah, you don't want to pollute your Orders table with what is essentially user interface state information. Here's how I'd clean up the code...

Or you can do this, where you save the filtered IDs only to a different table. Then drive the search result form off a query that joins those selected IDs back to the order table. In that case the search results are not actually driven by the filter, they are driven by the IDs that initially...

Just don't requery the result form on AfterUpdate, like... Private Sub Form_AfterUpdate() ' Me.Requery ' don't do this End Sub ... and *poof* the edited record doesn't go away.

Implement the system first. When it is working, then worry about barcodes. Barcodes are just a faster way to type. What are the fields, for instance, in your Parts table? If you can't answer that question, you are not ready for barcodes. hth

If you have a tPurchaseOrder table containing a field called CreatedByEmployeeID, which is a foreign key to a tEmployee table, then you can create a query, say Query1 ... SELECT DISTINCT CreatedByEmployeeID FROM tPurchaseOrder Query1 gives you the list of employees you need to show in your...

Populate your combo using a different source. Create a distinct query on the IDs you must have appearing in the list. Then join that query to your list of people, including in that result query a flag that indicates if that person is still eligible to be selected. You might prefix non-eligible...

If you use a subquery rather than DSum(), you won't need to worry about date formats, like SELECT fordate.ada, ( SELECT Sum(pamounts) FROM Amanat WHERE pdate <= fordate.ta ) AS SumPriors, fordate.ta FROM fordate;

Yeah, I use the AI all the time, probably more than google, depending on what I am trying to solve. The AI can even write code, I mean, not that well, but I asked it: Can you write me a VBA subroutine to find a WorkOrder in the fWorkOrder form's recordset using WorkOrderID? It provided... Sub...

Excellent point.

have you refreshed the link, or tried to link it again and see if you get the same result?

I would never navigate in a recordset to perform a delete. If you know the ID of the row, and you are happy to perform a requery after the operation completes, use an SQL delete command, like... Private Sub cmdDelete_Click() Const SQL_DELETE As String = _ "DELETE FROM tContact WHERE...