tags:

views:

61

answers:

1

I have an 8AM Access macro that verifies certain SQL tables are up to date. For business logic reasons, the Access file is stored and run on both my local machine and a virtual machine. It's pretty simple and almost always runs without problems:

  1. Windows task scheduler kicks off an Access macro.
  2. The macro runs queries on several tables from our SQL server to find the date those tables were last updated.
  3. Results are saved to a table in the same Access file.

This morning, the local process ran fine, but the VM process didn't return any records (I'm pretty sure it crashed, but I didn't capture the error message). Can anyone guess why the process on the virtual machine crashed, but the exact same process on the local didn't crash?

Edit

I should add that everything on my local and the virtual run independently of each other.

A: 

Are you positive the VM process started? at 8:00 AM?

If the virtual machine clock was running slow, perhaps the VM thought it was before 8:00 AM when you checked.

HansUp
According to the task scheduler log, yes, it did start at 8am and it was force closed 10 minutes later because it was still open. I'm inferring from this that the Access query threw an error which halted the entire thing until the task scheduler closed it.
PowerUser