Search results

Good,glad you got it going. As for batch files, know em, love em, use em .... You can do a search on google and find lots of sites to read up on syntax, usages , etc. I use them to kick off Windows Script files to process and move files, load and retrieve data from dbs, send status messages...

Mine worked with when i typed the full path name to access with the double quotes and removed the quotes from around the path to the db because it had no spaces in it .....

I may have misled you, but double check the name of the EXE file for Access. It probably should be MSAccess.exe ....At least that's what both versions i have say ....Oooops.

Can you post your batch file so i can see what it's doing? Now i've gotten a little confused on what you are wanting to do. I interpreted your desire to be 1. Delete records in table before import. 2. Import records. Did i miss it?

Note: do all your testing on a copy of your production file .....dont want to accidentally whack the wrong thing .... If your macro is trying to execute the function you listed, be sure the Macro is trying to RunCode .... try this to remove the records .. Function ClearRecords...

Since you are already using a batch file, why not add a line at the top of the batch file to open the access db and execute a macro that deletes the records in your target table. Make sure the last line of the macro closes access.

Glad you got something going. Right off hand, i dont have a way to change the mouse pointer. i have never had the need since my vbscript jobs all run on a schedule and no one is sitting and watching them .....

When you kill the object refering to the access app, that's probably killing the instance of the app as well. To do what you are trying i would try the following (not tested ) but you can test ...BTW, this assumes an installation of Access 2K dim wshShell2,result,strOfficePath,strDbPath...

What is it you want to do with the db? Just have it open for use?

Here's what i see you might want to check out. 1. With vb script, error handling is not like VBA. Essentially you have to declare a variable, and after each line of code that does something, set the variable = to the err number, then call another sub that handles the errror. Also, each sub...