Hi,

I used to run MS Access macros in the following way with a batch file without any problem.

"C:\Program Files\Microsoft Office\Office11\MSACCESS.EXE" "D:\myMSAccess.mdb" /x Macro1

Rather than bat files I'd prefer to have this in VC so I tried the office macro, but without success.

When I run the task, it keeps running, but nothing happens. I saw that in the Windows process MS Access is started, but it doesn't finish (the task also remains on status "Running") even though it should complete in a few seconds.

Any suggestions?

ciao

Luca

Hi Luca,

are you running 32 or 64 bit system? Which version of office are you running?

---

Win32 running Office 2003

only peculiar thing is that it's a virtualised machine, but that shouldn't have any impact I'd guess

ciao

Luca

Could you send your file and macro settings (from VisualCron screenshot) to support@visualcron.com?

---

will do that on Monday

Hi,

I checked the task log. After starting task immediately goes into error with:

Exception in Task: You entered an expression that has an invalid reference to the property Visible

any idea what that might be? Anyway, see enclosed the screenshot

ciao

Luca

Hello,

any update on this one?

ciao

Luca

Here seems to be one resolution. You need to add an event in your code:

http://support.microsoft...spx?scid=kb;en-us;841916 

---

mmm, this is strange...

the macro only contains a SetWarnings = No and then it runs a simple delete query...

I'll try and dig around, this seems strange

I did a bit more troubleshooting, but nothing interesting...

I actually ran a simple Macro that does nothing (executes some VB script with no actions) and still the error occurs. I am really thinking this might be due to way VC handles the call to the Macro as a simple batch commands works without any issue...

any idea?

ciao

Luca

As we are running the Macro in the background from a service account it is important that it is hidden. Otherwise you will get UAC warnings etc from later operating systems like Windows 7, 2008 and Vista.

So, to overcome this we set the Visible property to false. I guess, that the problem is that you need to add the event (described on the Microsoft page) to you VB-script in order to get it to work.

Did you try that?

---

Hi,

please test the latest version regarding this issue.

---