Search results

another solution could be.... debug.print DLookup("PartID", "qryPartsToStock", "qryPartsToStock.ManufID=" & [Forms]![frmPONumbers]![frmPOItems].[Form]![comboManufacturerID]"& _ " AND qryPartsToStock.ManufPN=" &...

dim rs as dao.recordset set rs = currentdb.openrecordset("yourquery") Debug.print rs!PartID msgbox rs!PartID rs.close set rs = nothing Something along those lines?

Proper indentation of your IF/else/endif and other places really helps to keep track of where you have what.

I am guessing that the check for partnumber only is checked when the first check for Value_Stream fails. Proper indentation shows this problem Private Sub cmdSaveEmail_Click() If IsNull(Me.Value_Stream.Value) Then MsgBox "Please select a Value Stream", vbOKOnly, "Warning"...

stDateField as your statement is, is expected as a field inside your report. I am guess your field inside your report is "date worked" << PS will ignore the naming problem. Try: stReportCriteria = "[Date Worked] Between #" & stStartDate & "# And #" & stEndDate & "#" Or.... maybe as you...

Why use a DLookup at all, what is your goal? D functions have their time and place, but 75% of the time there is a (much) better way of doing things.

Most likely its a disconnect in your eyes fooling your brain into thinking .... a small typo somewhere that you were unable to spot txtCertifcateNumber

@Pat Hartman How would deletes be allowed in this case?? Or most any case, surely one would mark records as "obsolete" or "in error" or what not over deleting data.... Agree that DMax will guarantee results better than DCount on the other hand proper data management should be enforced....

Which has been the case since the start of the thread.

Which is why I highlighted where to look instead of putting in all kinds of fixes.... " Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime. "

You missed one ;)

Make your code readable, it will help you debug it.... Me.TCMP.value = FormatIndian(Nz(DSum("Chamt" , "total cmp" , " finyear = " & [COMFY] & _ " and section = " & [TXTUC] And "[settelment_date] between [Text0] and [Combo4]"))) With each of the red coloured somethings wrong The blue...

Well 3 fields is a good idea... 2 fields is a good idea, your sequence number and your date field. At the root you only need these 2 fields. Having 3 fields, year, month, sequence is a halfway solution... your still destroying information. (the day part the date) which is generaly a bad idea.

Dont want to knock @arnelgp 's work, his solution certainly does work, but custom keys are worse than bad, make sure you use an autonumber inside your database as the "real" primary key. While @arnelgp 's work works, I disagree with his approach. Because it limits you to 0001 = 9999 returns...

Used for nothing, its braggin rights only. I once wanted to appear on the top posters lists, but I dont post in the watercooler nor on "hello" posts Now a days I dont frequent the forum as much as I used to back in the day. Still seriously believe that Access and Excel are the most underrated...

No one ever remembers me :(

1 you need to simply make an other column to sort on, you format said column as YYYYMM and order by that 2 same as 1, but you keep the original unformatted date and filter by that ... put in the where clause: >= dateserial(year(date), month(date) -1,1) this will make >= 01-aug-2020 for the...

sorry but no no no no no... mixing characters and numbers and expecting proper results.... no no no. Split your columns as per my earlier post, make your own life easier by so many ways ... 4 seperate columns for four seperate needs. KISS Keep characters characters Keep numbers numbers Keep...

Concure with other contributers, use a autonumber inner database key for inner database needs. Compound user keys like this are best of storing in seperate fields, thus in your database use atleast two fields or even three or four fields to store the seperate character part(s), Field 0...

Insurance people Gas and Light people Notary Suveryor (of real estate) Estate planners Investment advisors Pension funds The of "white collar thugs" that will make you overpay for most anything is long