Search results

Combo boxes should not be used for multi select. use a list box.

make a form, put a text box,or combo: cboName, all queries will now use this box as the param: select * from table where [clientName] = forms!fMyForm!cboName put all qeries in a macro, run macro.

use the BUILDER to create the code for assigning the text box (it wont get it wrong), Normally it would look like : = me.subformName!form!txtBox or you would run a query to add data to the suform textbox. can you send the code to the function ToUGX() ?

save the report, then email via email. put a list box on the form, this will cycle thru the names in the list, create their report, then send it from the email in the list. '------------ Public Sub ScanAndEmail() '------------ Dim vTo, vSubj, vBody, vRpt Dim vFilePath dim i as integer vRpt =...

Ah, the Text981 cannot be bound to a field. it must be unbound

Is ID a numeric field? is the combo bound to the correct column?

What error?

Why not just show a hidden label on the form? “Processing...” or other it’s in the same form as the event, so it knows when the event is over.

This looks correct...what error msg? Is the box name correct? Me.vendorname where is the code? In form load? In other event? is the return field name correct?

a count should never be null. is clinic code a string? Then it’s: Me.total= DCount("*", "[MRN_number_Of_PO]", "[Location - Clinics Code] =‘" & Me.Combo2 & "‘ and [Year22] = " & Me.Year1)

once you close the form, the code in the form evaporates and shouldnt be able to run. make the last step CLOSE FORM

rst.recordcount wont count unless you got to the end, so use DCount(...) lbl.visible = Dcount("*",me.recordsource) = 0

You can link in the old tables (via odbc ) and have them like: tCustomers_Old, etc then you can run queries against both tCustomers & tCustomers_Old

dont use: Me.ViewingForm.SourceObject = "frmblank"

you dont set focus on a form, you set it on a control in the form. (so the 1st line is useless) Line 2 should work if you have the names correct. Did you use the BUILDER to get this path?

use a continuous form to show all records, then when the user fills in the boxes, then clicks the FIND button, use vb to build the where clause: sub btnFind_click() dim sWhere as string sWhere = "1=1" if not IsNull(txtBox1) then sWhere = sWhere & " and [field1]='" & me.txtBox1 & "'"...

click windows start, type: calculator, enter.

these are just the system's way of spacing the fields when you use auto form-build, it lays out all fields and labels and columns. you can just copy an existing one and paste where-ever, or use an empty textbox.

Never run single step macro. just run the macro: in the macro: ImportExportSpreadsheet, excel workbook queryName filename yes or in VB code: vFile = "C:\mypath\files\ExportFile.xlsx" DoCmd.TransferSpreadsheet acExport, acSpreadsheetTypeExcel12Xml, "qsMyQuery", vFile, True

in 1 single report that is nothing but subreports, put in N subrpt boxes each mapped to a report. hand assign each subrpt to a source, --- or ---- in a table put in the names of all the reports to use. in vb , open the report in design, cycle thru the table of reports assign each to a subRpt-N...