P
PeteCresswell
Got a time-consuming batch process that needs tb done every day, but
does not need any user input - only the current days date (computing
yields and daily accruals for fixed-rate securities).
There's a lot of code, so I want to keep everything within the current
application.
Somehow, I want to make it run at, say, 2:00 in the morning every day.
The LAN people say "Windows Scheduler and a .BAT file".
That makes me think of something like:
START /B /HIGH /MAX "Collateralized Debt Obligations" MSACCESS.EXE
"%AppPathLocal%" /ini "%IniPath%" /wrkgrp "%SecPath%" /Excl /Cmd
%AppDirLocal%
Which would open up an instance of the front end, feed it a command
line parm that tells it to do the accrual/yield update thing and then
close itself.
I'm guessing that Windows would run it under some sort of "System" or
"Admin" UserID.
Is it that simple?
One thing I'm obsessing over is that, on a production server, if this
thing goes berserk for some reason I never considered, it could
effectively bring down the server.
does not need any user input - only the current days date (computing
yields and daily accruals for fixed-rate securities).
There's a lot of code, so I want to keep everything within the current
application.
Somehow, I want to make it run at, say, 2:00 in the morning every day.
The LAN people say "Windows Scheduler and a .BAT file".
That makes me think of something like:
START /B /HIGH /MAX "Collateralized Debt Obligations" MSACCESS.EXE
"%AppPathLocal%" /ini "%IniPath%" /wrkgrp "%SecPath%" /Excl /Cmd
%AppDirLocal%
Which would open up an instance of the front end, feed it a command
line parm that tells it to do the accrual/yield update thing and then
close itself.
I'm guessing that Windows would run it under some sort of "System" or
"Admin" UserID.
Is it that simple?
One thing I'm obsessing over is that, on a production server, if this
thing goes berserk for some reason I never considered, it could
effectively bring down the server.