Search results

Perhaps put up a physical form example. All else is theoretical.

Good spot.

You know, the only time I use ! is in queries, forms, and reports. I prefer never to use it in VBA. Would much prefer to pick up as many coding errors as possible at compile time rather than run-time.

I don't, as it's not really been an issue where I am. However, although it may take a bit more work, you could design forms for different screen resolutions and then do a check via VBA to determine which resolution is being used and then load up the relevant form tailored to that resolution.

Quick thought: have you tried using the date delimiter when using dates as criteria? (And brackets around that awkward underscoring in the field name...!!) intArticleID = DLookup("ID", "tblArticles", "[Sourcing_Date] = #" & ![Sourcing_Date] & "#")

As i said, hasty example with little thought put into it. However, would be helpful if you therefore gave some information on your actual table structure and, if any, your thinking behind it.

Yeah, I was a little hasty in my first example and subsequently deleted it. :o

Quick example, which may be of some help in signalling a direction to take.

Looking at that SQL my first concern is that it looks like you have a table called [2015 Holiday]. If so, why? Surely a single Holidays table covering every possible year would be easier to work with?

Is a particular line of code highlighted?

You can do it in the form's module. That's where the Form_Load event is.

First, you may be better to use fOSUserName() - google it! - for a more robust user name formula. Environ() can be spoofed. Now, what you want is for your form to check the NewRecord property. In your form load event, try something like: If Me.NewRecord Then Me.txtYourTextBox.Enabled =...

Start by googling for fOSUsername(), which is some code that will give the user's name. In the table that holds the user data, add a field for their system ID and add them. Then, on your form, you can do a comparison with the user selected and their fOSUsername(). Plenty of threads on this...

Also, if you do a little check like this...then you can fill out the year completely, assuming that every boat year will be 19. "VALUES(""" & fieldNam & """, """ & IIf(Len(arrayVal(1))=2,"19","") & _ arrayVal(1)) & " & """,""" & IIf(Len(arrayVal(2))=2,"19","") & arrayVal(2)) & """,""" &...

Turn off your On_Error statement and let us know where the error is actually happening.

Just to verify one thing...when you say combobox you actually mean a listbox, right? The reason I ask is because a combo can only have one value, so when you talk about multiple values...well, you know.

That wouldn't CC but instead send the email to somebody@ntlworld.com and the person whose email address is in the field. Using DoCmd.SendObject you get a To and an CC parameter. DoCmd.SendObject , , acFormatRTF, strEmailAddress, "somebody@ntlworld.com", , strSubject, strMessage

Welcome to Access, which is not Excel. Something about the way you describe this project/issue suggests that you are approaching table design in Access the same way you may set up an Excel spreadsheet. This is not the approach to take. There is no VLOOKUP() function in Access. There is domain...

Goes against some basic database design, though. You'd have been better just using queries to select the relevant company info from your main table. Okay. Here's a quick overview. Tables store data. They can have fields and rows. Queries question or manipulate the data. You can get SELECT...

Ah, you were passing the control name. Got it! As, I see, have you now.