Search results

someones going to ask you why you want to do this... however, I've had to do it also... here's some code that will get it done (expand the case statement to handle the number of field you need to deal with) Function ProcessTable1() Dim db As Database Dim Table1, Table2 As Recordset Dim...

dS, never used it but you can get the tables in a db via the tabledef structure. Involves looping through testing each to see if they look similar to what your expecting. Some searching about tabledefs will turn up how to do it. However, since this is part of your other thread, why don't you...

dS, if you want to capture that 1st row of data, change your import specification so that it doesn't expect fieldnames (not sure if you've done that). If that imports ok then do the following: in the loop retrieving the files in the folder: - Use a delete query to empty the import table -...

alternatively, upgrade to Acess 2010, just read a few things that indicate that can do it natively! That would fix it! :)

no idea... it might not be able to do it. Time to google something like 'print without prompt using CutePDF" (swap CutePDF for whatever you're using).

sounds like it's the PDF printer software that's asking for the name (one I use does that too). Might have to see if you can get that to accept the default name (created from the report name so you'd still need to create a report with the name you want) and just create the file without the prompt.

Chris, yep that works! Will need to remember that just in case!

I would investigate seperating the call to the subroutine to get the text and building the string that you want to create with the database value (CustomerName) in it. So you'd have something like varSubject = DLookup("SubjectLine", "gblSysLaptopSwaps", "ControlRef = 2") varText = varSubject...

Haven't tried this... But, maybe you could use the 'copyobject' method to create a new report with the timestamp as part of it's name then export that. Delete the temp report (object) to clean up after yourself.

Never encountered the need to do that, however I wonder if you couldn't have two fields on the report [Field7] & [Field8]. [Field7] would be where Field4 is and it's 'control source' would be =LEFT([Field4],40) (or whatever the syntax is) and [Field8] would be on the second line next to [Field6]...

hehe! I'm still using Access 97 (although that screen shot was in Access 2003... have it installed at home but use '97 at work!) so any thing I suggest is going to be 'old school' methods :) Cheers, Nige BTW, Bob, I'm new to this forum and have been reading lots of threads and see your name...

I think you're going about this the wrong way. A report should be linked to a table or query via the "Record Source" parameter of the report. There's no need to create your own loop. In your case this should point to "Audit Issues 2009". You then have all your IF statements in the...

1st re-check your query, the report will usually only show what the query is selecting. Sounds like your query is creating the duplicates, you might have duplicate data in the tables.

For future reference, another way of achieving this is to have a table of valid selections (either created with a query or maintained seperately) with a Yes/No field that you tick on/off to select the selections you want (displayed using a form if you want it to look nice). Run the report (with...

maybe just a syntax issue. What I do in circumstances like that is create a query in query builder so that it works, then view the SQL and copy that into my code. I tried a more basic example of what you're doing (just using the start and end dates) and it looks similar to yours but did work...

If this is just a one-off data clensing task, create a query with both tables, join the like fields and make it a one-to-many join (show all records in table X and matching records in table Y). Add your joining fields to the query and in the field from the many table (Y in this case) put "null"...

dSurvivalist, I did a similar thing recently which you might be able to adapt. I have a macro with the following 1. Set warnings off 2. Check user really wants to proceed (this replaces existing data so I give then a chance to back out) 3. If yes, then delete data in table using a query 4...

while that's true (and I've used that method many times), sometimes eyeballing the data gives you a clue to what's wrong, or that the data is not what you think it is (different layout... could spot that in seconds). YMMV

another way if to find an editor called PFE (http://www.lancs.ac.uk/staff/steveb/cpaap/pfe/) which will open such a file and has a jump to cmd (CTRL G I think) Cheers, Nige

Hi.. another newbie! Have obtained many hints from the forum and saw something I could answer so joined up. Now I can't find it! Ohh, well, maybe something will come along I can help with. Cheers, Nige