Search results
-
Y
When form control is empty
This is more a tip, and a personal preference, so feel free to ignore me!! I prefer not to call my combo's Combo86 (for example). I will change the name to comboStartDate. It makes it much easier to debug or alter your code at a later date, and also for others to follow your code if...- Yarp
- Post #6
- Forum: Modules & VBA
-
Y
When form control is empty
before you run your query, check the values. Something like: If Me.Combo86.Value = "" Or Me.Combo88.Value = "" Then Msgbox "You are a stupid user" Else Your code here to run query End If I am assuming you are running the code from the form and that Combo86 and Combo88 are null...- Yarp
- Post #3
- Forum: Modules & VBA
-
Y
Macro that creates a PDF and save it on a specific folder
Have you tried creating two private subs that are called by the public sub (the macro run by the button press). By seperating into two seperate processes, the print then the save, you may get around the issue you are having. Apologies if this doesn't help, but I don't have a specific answer...