Recent content by PatrickJohnson

I'm trying to apply some conditional formatting to some rows in an excel spreadsheet via access vba code. basically, i have a list of tables, lets say A thru D. I have a routine that exports these tables to separate sheets in an common excel file. I am doing this by looping through a recordset...

Thanks for the reply. I will give this a shot. However, I have to admit I don't like sprouting up modules and code in other files. When I run a routine, I would prefer all the code be performed within the Access application. There has to be a better way than remaking a new file every time. And...

Nope, same issue: "Do you want to replace the contents of the destination cells in PARAM?" It build the new pivot, but then attempts to place new data on the original sheet. Did the same thing when i tried the same process.

So, I have a report I send out monthly. The end user needs both the source data and a pivot table summary, and both must be in Excel. So my thought was to export the source query from Access to an Excel sheet, then use Access vba to build a pivot from the data. Then the problems began. First...

easiest way for me was to load the data from the word table(s) in the document into arrays then parse that data into fields on a table. I did it with some help in this thread: http://www.access-programmers.co.uk/forums/showthread.php?p=716286#post716286 Then you can play around with the data all...

good to know! Thanks! :)

the "iif" does not work in code, it only works in the design view of queries and in form controls. if this is code, it would be what Bob posted, though i tend to put in ELSE: END IF instead of just End If, but both work fine.

To answer your question more directly, yes the code needs to be housed in one way or another, either as an argument in the DoCmd.RunSQL part or in a string field. However, you don't have to reassign variables as you have above. If I have a dinky bit of one line SQL code, i do as above...

I got it to work! I put in the declaration you mentioned, but was still getting some object errors. Here is the code i ended up with, look it over for efficiency if you don't mind. Also, I've got some carriage returns or spaces or something in each field with the data, how do i get rid of...

Okay, i got an error now when running the above code. When it gets to this line: i = ActiveDocument.tbl.Rows.Count I get an error saying "Object doesn't support this property or method." Any ideas?

yeah, i did that and that solved my compile error. when you have opportunity though, i would love a better understanding of the best paractice.

Sorry, i should have been more clear. I haven't gotten around to testing the code you posted until now. Here is how i have it written: Dim wrdapp As Word.Application Dim wrdDoc As Word.Document Set wrdapp = New Word.Application wrdapp.Visible = True Dim path As String Dim i As Integer Dim...

i'm getting a compile error (type mismatch) on the following part: strArray(x, y) = ActiveDocument.Tables(1).Cell(x, y) any ideas?

Well, if it were an option to change the formatting of the output i'm receiving, I would have just made it come out in a csv :) Unfortunately the tool that generates the report was written by third party and the company is not interested in the huge fees to have it rewritten when some...

so just so i'm clear, this is meant to add the data from the rtf directly to an access table, correct? If so, that would certainly reduce the headaches.Arrays are pretty foreign to me though, so while I will likely implement this solution, could you explain in a little more detail what exactly...