Hanging .ldb

[Guest]

I have an access 2000 database that has numerous links to other tables in a
Teradata database far away. When I or my users use the database, they press
two buttons sequentially to perform two major functions.
Function 1 is to manipulate the data in the linked tables and create some
local (to this database) tables
Function 2 is to further manipulate this data and create some reports from
the local tables
When the Database is accessed and used by myself or the other users (via
Citrix) everything works fine The system compacts itself and shuts down as it
should, however, when I set it up on the Task scheduler of the remote server
where it resides and use the command line option of "MSACCESS.exe /x
("autoexec macro name") \(location of the file)\(databasename.mdb) and the
program runs at the appropriate time , it runs as it should except that it
does not Compact and shut down it also leaves the .ldb out there. I have the
"Compact on Close" checked and even reset the option in VBA code I also have
a section of the code go along and check for open forms and then close them.
Tools-Options-Advanced are ;
- No Locks
-Shared
- Open Databases using Record Level Locking= unchecked

I have to come in each morning and shut the program down via Citrix and the
Remote TaskMgr.

What am I doing wrong ? it works fine if you run it manually. I even created
a button that runs the Autoexec macro from one of the forms it works right

Help !!

 

[OldPro]

I have an access 2000 database that has numerous links to other tables in a
Teradata database far away. When I or my users use the database, they press
two buttons sequentially to perform two major functions.
Function 1 is to manipulate the data in the linked tables and create some
local (to this database) tables
Function 2 is to further manipulate this data and create some reports from
the local tables
When the Database is accessed and used by myself or the other users (via
Citrix) everything works fine The system compacts itself and shuts down as it
should, however, when I set it up on the Task scheduler of the remote server
where it resides and use the command line option of "MSACCESS.exe /x
("autoexec macro name") \(location of the file)\(databasename.mdb) and the
program runs at the appropriate time , it runs as it should except that it
does not Compact and shut down it also leaves the .ldb out there. I have the
"Compact on Close" checked and even reset the option in VBA code I also have
a section of the code go along and check for open forms and then close them.
Tools-Options-Advanced are ;
- No Locks
-Shared
- Open Databases using Record Level Locking= unchecked

I have to come in each morning and shut the program down via Citrix and the
Remote TaskMgr.

What am I doing wrong ? it works fine if you run it manually. I even created
a button that runs the Autoexec macro from one of the forms it works right

Help !!

I can't answer your question, but I wonder if a close command in a
timer event might do the trick.

 

[Guest]

Access has never worked well with Task Schedular: Task Schedular
has never worked well with Access. It has to do with the kind of
session that Task Schedular creates. So if you were trying to do anything
complicated with Task Schedular I would recommend using a third party
task schedular instead. By necessity, third party task schedulars run in
ordinary login sessions.

You haven't described how Access is supposed to shut down.

My guess would be that you have an unhandled error.

I wouldn't use Access.exe for that anyway: I would use one of the
data access objects: DAO or ADO. Access.exe is not designed to
be run from a schedular, and it is only necessary to use Access.exe
if you are producing a report (as snapshot or pdf ).

The script that you have in the macro's can be written in VBS or Cscript
or VB6, using DAO or ADO. It will run faster, lighter, and smaller
using just the data objects And VBscript or Cscript or VB6 with ADO
or DAO work much better in Task Schedular than Access.exe does.

The only disadvantage is that you won't be able to put User Defined
Functions inside your Queries.

(david)