Search results

You have complicated things more than needed. Change the query and code behind button as shown on revised database. The report's query has as its criteria the form's client ID. The send report command takes the email address from the form.

Can you upload screen shots of what you have so far?

Try this: stAppName1 = "C:\a folder name\pdftk.exe " & combine_files & " cat output C:\folder where merged file will be\merged filename.pdf"

Your code below the If DCount statement should look something like this: If Msgbox("This reporting month already exists. Do you want to overwrite the data?", vbYesNo) = vbYes Then DoCmd.RunSQL "Delete FROM Months Where Months.Reporting_Month = '" & repmonth & "'" Else followed by the rest...

This might be more than what you can chew at this time, but it's a start. Once you have your input form designed, in your button's click event, whatever you happened to name this button (Ok, Save, Post, etc.) you call this function passing it the parameter you see fit, in this example, you're...

Could you share with us a copy of "scrubbed" database so we can be of most help?

The following pseudo code might do the trick. Place code in a subroutine or function, and call it from the button click event: Dim aFSO As Variant Dim strFileNameAndPath As String Dim strFileNameOnly As String Dim strNewFilePath as String Set aFSO =...

Could you share with us a copy of your database (scrub it if you have sensitive data). This way we can see what you're running into.

Tell us why you are checking if a form is "visible"? And if it is, then what, and it isn't what?

Pardon my ignorance, but where does one find FindAsUType function?

Have you thought about inserting a sub-form in the main's form footer, keeping the footer hidden until such time the maintenance is flagged as incomplete? This way all your information is in one form, no opening or closing forms, except for the main form. What follows are two routines, one to...

As for the renaming, why not use the aFSO.CopyFile Source, Destination then use the Kill command to delete the old file?

Have you tried creating the query in the design mode, and then making this query the form's record source?

Have you tried to add, for those fields where there's a possible null value, the following: Like "*" & [Forms]![PawnProperty_PawnerQueryForm].[Make] & "*" or ([Make]="" or [Make] Is Null)

How about: Me.Combobox2="" This will clear the text area of drop-down

In the racks drop-down, make its RowSource equals to your CI "control source" and not to its row source. This is important, your dependent drop-down should draw data based on its parent's drop-down control source. Make sure that the parent and child drop-downs have a related field; the child has...

Could you share with us some screenshots?

Is [DUED] known? If so, if I use, say 1/12/1999 and today's date, and divide the result by 7, the answer I get is 765.414 This number represents weeks. I'm not sure what exactly you're trying to calculate. A date in the future? In the past?

I would put code on the OnCurrent form event. This code, using a simple If statement, would validate the result at the cases picked. If (Cases Picked>Cases Required) then Call the PlaySound routine End If Unfortunately, this website does not allow me to post links. I have one that shows you...

On the AfterUpdate event of your drop-down control, insert code that validate choice and then it would make a given tab visible or not. ' Tabs are zero-index, meaning the first tab is zero, second is 1, etc. Me.tabMain.Pages(1).Visible = False ' This will hide the second tab