Recent content by Roku

I've made an example DB for you which has three tables. It's not clear to me what your DB is for, so I have made a number of assumptions (see table of assumptions) The query 'qProcessList' is used to allow selection of material type, joint type and welding process from the available...

Glad to have helped :) You might consider putting .Subject = Nz(DLookup("EmailSubject", "tblEmail"), "")in case DLookup returns Null. Note also that I have removed the square brackets because they're not necessary and dropped the third parameter, because it's optional.

OK, that helps. :) I envisage three tables here: 1. Table of welders. 2. Table of weld processes etc (per previous message) 3. Table of certifications by welder. The third table is essentially the link between two sets of related (but independent) data. It points to welders and processes...

Without knowing what tblEmail is, my guess is you need this syntax:.Subject = Nz(tblEmail!EmailSubject)this will work if tblEmail refers to a Recordset and EmailSubject is a field within that Recordset. If tblEmail is, as it's name suggests, a table, then you will need something different. You...

The diagram helps - thanks.:) It appears that there are six basic combinations (2 material types, each with three welding processes). What the diagram doesn't tell me is the dimension ranges for those six. I assume the welding process is governed by the choice of material with diameter and...

Table2 design is inappropriate for what you are trying to achieve. By repeating field groups for weld process and dimensions, it becomes much harder to manipulate, which is why you are having difficulty. A better approach is to have a reference table which lists each material along with its...

Sorry for delayed response. I think the syntax error on the 'Else' part is from the way you have laid out the code. What you have added is structured like this:If <condition> Then <true action> Else <false action> End IfChange this toIf <condition> Then <true action> Else <false...

The error is because 'olapp' is not set. The two places where it was set in the original example are commented out. Please provide some context for what you are trying to do, so we can provide more constructive help! :) Are you putting this code in Access or Outlook?

I got a chance to look at your code again. A simple way to do what you want on the welding process etc. is to split the choices and check each in turn. The following does this:Private Function checkWelder() Dim strMessage As String Dim ctl As Control Rem set ctl to point to the active form...

Forgot to answer your other question. That needs some work to unravel, but I can't do that today ... maybe tomorrow afternoon. A quick look suggests you should have a table of material types with welding processes, with the combo box used for selection. I envisage the user selecting a material...

I think you have your test conditions mixed up. The basic logic is to test all conditions, adding errors to the message at each failure. Having completed the tests, check the message to see if it has content and display if it has. What you are doing is checking the first value and then...

Now you tell me you are an Assembler programmer, I see the sense! :) I cut my teeth on Assembler in 1972, using a CDC3300. I later went on to Burroughs B3500. COBOL took over after that. No such thing as a screen in them thar days :cool:

The screen resolution is too small to read clearly, but I can see your Combo Boxes are shown as 'Unbound'. I can't read the error message, but my guess is that it's related. If you change the Control Source for each Combo Box (in its Data tab) to the relevant field in Table1, that should fix...

I don't understand what you mean by this? The control name is set at design time, so you have to find out what's there at run time by some kind of looping mechanism. In your earlier post you said: As you probably know, controls have a Tag property - but I got the impression that you meant...

That line and the preceding one tells you that the table starts out empty. This part updates the table. The 'Else' part creates the new records; the 'If' part updates records created earlier. The clue here is the use of Recordset GrpPages, which was set in the Report_Open subroutine.'Find the...