Recent content by Chrafangau

Try =IIf(IsNull([Acting Principle]), [Principle], [ActingPrinciple])

Not quite, you want =IIf(IsNull([FullNameP2]),NULL,[FullNameP2]) And then any other fields on the same line are =IIf(IsNull([FullNameP2]),NULL,[OtherSource])

Yes, it's the table column. If you have issues with it just use Tablename.[nullcolumnname] [fieldsource] is whatever column you want the data for the text box to come from if the field you're checking for blanks is not blank. It can be the same as the field you're checking. As for the labels...

Thanks heaps Paul, this served the purpose perfectly. And now I can use checkExistance for a bunch of other spots where I was stuck. Really appreciate it. And as for the oddity of all the queries, I ran into an 'expression too complex' issue a while back that I worked around with a series of...

The way I dealt with this was to determine which field would be null if the line didnt have the required data, then create this code: =IIf(IsNull([nullcolumnname]),NULL,[fieldsource]) Set this as the Control Source for each of your fields, replacing fieldsource with their respective sources...

Never mind, the issue with writing to the queries was between the chair and the keyboard. Just a small SQL syntax problem that wasn't coming up due to error suppressing.

I'll see if I can implement that suggestion re. the appends, it makes sense. And you're right about the normalisation, though I dont think there's any way to do that with my current method of exporting other than manually, so given my time constraints I think I'll have to let it slide for now...

I have used your code as the basis for writing a module that generates my union queries, and it works really well, so thanks heaps for setting the groundwork for that. As for normalisation....I'm honestly not sure how to normalise this mess. The only thing I could take out might be the date...

Taking your first post, I suggest adding a second loop around the first, to set the focus to the next column, so on and so for however many columns you have. This assumes you know how many there are in advance: Dim rst As DAO.Recordset ' recordset for category data Dim pageno As Int 'Page...

What would the best way to open a series of queries, if you aren't sure how many of those queries there are? I have the following: DoCmd.Close acReport, "SCEFReport" DoCmd.OpenQuery "ClearTBLQuestions", acViewNormal, acEdit DoCmd.OpenQuery "Q1append", acViewNormal, acEdit...

Sadly, both methods presented above have given me 'Expression too complex' results when used for more than ~10 fields. Access just does not seem to want to handle these queries.

Out of curiousity...what happens at 110 and 12013?

Good news is that, if you want what I think you want, no VBA code is needed. Just make a select query that pulls the fields you want from the table of results, and at the end of the SQL file add the line: WHERE tablename.customer = Forms!formname.dropdownboxname AND...

Thanks for the response, I'll look forward to trying this out come Monday.

I would agree with you on the basically screwed front, except that it all already works. I just had to break the union query into ten little bits and append them onto a dummy table one at a time. The data, at this stage in the process has already been through 2 other queries that filter out the...