Search results

That may work. The only other thing I can think of is the name of the sub doesn't match. In all of my trials of doing the same sort of thing, I never got the error you are seeing. I don't have access to some archived stuff where I had done exactly the same setup. Like I mentioned, I modified...

I am not sure about 2010. I know you can import custom bars in 2007 and utilize those without any issues - I use these as right-click pop-up menus. -dK

I believe it is a reference issue ... You are trying to do something from Sub MH2 and apply it to Sub MH3, however, you are not supplying the path from MH2 to MH3 (the Parent). I've done the same as you before but different implementation (from a module function) so I am swagging here, but...

I disagree. I think the OP is suggesting that the user opens the job form and assigns customer to the job. As PNGBill stated, what many are used to is to go to the customer's form and add a new job from this form (while seeing all previous jobs in a subform). I have applied the technique...

Think about it like this ... different human languages all say the same thing except with minor nuances, so I'd probably take a standard DBA/Coder template because everything you do in Access is being done in other languages. So is someone who holds themselves out as an .ASP programmer better...

And here I was thinking it was my ex-mother-in-law. :D

I think I stole it off of RuralGuy a long time ago and put it in my list of favorites. Funny though, sometimes when I am struggling with dates and times I have found myself googling up brian's name since his understanding is much envied. -dK

In the form properties for the KeyDown event, you can try ... If (Shift and acCtrlMask) > 0 And KeyCode = 80 Then KeyCode = 0 Then set the Key Preview property of the form to 'Yes'. -dK

Here is a good resource. Skip down to the 'Time, adding and subtracting ...' -dK

Awesome .... glad it is working for you! Good luck! -dK

Are you using the arguments supplied by vbaINet? That is, if you have DCount on a code line and nothing else, you will get that error. You have to provide an argument for it .... If DCount(allofyourstuff) <> 0 Then ... the record exists else ... it doesn't exist end if -dK

Hehe .. I like her sister, too. :cool: I wasn't sure if you (or someone) wanted the full zip (in the future) and was going to actually fix them or not. If you want to clean it up permanently, use the same syntax in the "Update" row on an update query. -dK

Ah .... here is something when dealing with apostrophes and quotes and such with strings. It also has another link (on DLookup) on it and both pages may provide some insight now and when moving forward with your project...

You betcha. Good luck on your projects! -dK

I would suggest just trying one. Let that one work error free. Then add another and debug it, and then add another condition, etc. etc. I would point you to this article. Scroll down to the 'multiple criteria' section. HTH, -dK

Aye ... I think that bit is called 'Layout'. I would guess that yours is set on 'Tabular'. The form wizard will normally used 'Stacked'. The layout can be found under the same pop-up menu when you right-click the control. I assume that these all have their purposes. :confused: The only one...

I wouldn't jack with the original fields but use a variant to retrieve what you want. For instance, in the QBE go to the last column and put in something like .... ShortZip: Left([ZipCodeFieldName], 5) Change the ZipCodeFieldName to whatever the field name you have that holds the zip...

You betcha. I probably would have referred that initially but thought you were only dealing with two criteria. Once you mentioned the complexity bit, that one sprung to mind. Apologies, but glad you got it working straightaway! -dK

Here is an idea for (1). Supposing multiple assignments for states and such I further suppose each user is unique by some field (name, ID, etc). You could use a subreport based on your user name (or ID or whatever method you use) and the state's assigned to you (or that ID). Then set the...

My guess would be because of the anchoring you have on those controls. If you right click in design view, you will see the anchoring on the pop up menu. If you have selected some point on the form, the control will automatically stretch per the selection when you maximize the form. You can...