GDGarth's approach is good - I use similar for some of my applications.
Another approach I use (alluded to in your first option in your post) is to have my Access code create my connections and do my append queries (which I hard code). I pick up several files that I upload to tables - I get...
Ooo, yeah! You could write it to a password-protected doc (like "newpath.doc) that your code places on the user's drive if needed. The default would always be in the actual code (template).
I would try something like this:
If target_file not found in default_path then
look for...
Answer to ETID:
I prepare numerous reports each morning all from within Access. Preferred delivery to my users is Excel. By using this method, I can control everything from Access and it uses fewer resources. Plus since I mail out reports, I don't have to try to get around users not having...
Here is the method I use to dump a large (or small) amount of data to Excel from Access. The only time I do not use this is when I am only putting data into a single cell.
Note: The way my code is written, I operate on a single sheet at a time. If you use the Workbook object, you will need to...
Do I understand that you are bringing your records over to Excel one record at a time? If so, there is a much quicker way to do this... You can pull a recordset of the access table then dump this straight to excel. If you want, I have some code I could share to show you how I do this.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.