[AccessD] Scheduling an mdb to run using AT

Drew Wutka DWUTKA at marlow.com
Tue May 13 11:33:14 CDT 2003


Hey, if it works, it works.  The big advantage in this case, with a VB
service versus AT, is that you are using Access vs. VB.  Access is much
heavier on the resources then VB is, so a VB service that runs a data
crunching routine would be more lite weight then a full blown .mdb.
 
Drew

-----Original Message-----
From: Software Design & Solutions Pty Ltd.
[mailto:SDSSoftware at Optusnet.com.au]
Sent: Monday, May 12, 2003 9:14 PM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Scheduling an mdb to run using AT


Drew - thanks for that explanation. So if this code were in vb instead of
vba then I could look at building an NT service OCX and add my system as a
service.
 
OK - but for an mdb I may as well us AT?
 
Kath
 
 
----- Original Message ----- 

From: Drew Wutka <mailto:DWUTKA at marlow.com>  
To: 'accessd at databaseadvisors.com' <mailto:'accessd at databaseadvisors.com'>  
Sent: Saturday, May 10, 2003 7:23 AM
Subject: RE: [AccessD] Scheduling an mdb to run using AT

Pure VB codes almost exactly the same as VBA.  The syntax is identical,
there are just a few minor changes in functions (such as AddressOf is a
default ability in VB, and Eval is only available in VBA).
 
As far as the NT Service OCX, let me explain....
 
A service is something that runs on your machine whether you are logged onto
it or not.  (Once Windows has loaded it's device driver's, etc., then it
starts the services).  In 9x, services are just a registry entry
(HKLM\Software\Microsoft\Windows\CurrentVersion\RunService) (That may be
RunAsService...don't remember, and it's not on NT machines, which is what I
am using now...)  Any program can be placed there in the registry, and it is
run by windows as soon as it comes up....regardless of whether a desktop is
loaded or not.
 
Now, an NT service is similar, however, it's not a normal registry entry.
Services is part of the Administrative control panel.  (Control Panel -->
Administrative Tools).  That lists every service running on your machine.
>From that panel, you can start and stop services, you can set whether they
can interact with the desktop, or what NT account is used to run the service
as.  Pretty flexible.  However, to 'build' an NT service, requires callback
capability, since the system has to 'holler' at the service to start or
stop, etc.  The NT service OCX (ActiveX control) provides that callback
capability to VB.
 
Drew

-----Original Message-----
From: Software Design & Solutions Pty Ltd.
[mailto:SDSSoftware at Optusnet.com.au]
Sent: Friday, May 09, 2003 3:46 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Scheduling an mdb to run using AT


Hi drew - this is an mdb - the basic process it performs is to log on to an
external system, read in some data, manipulate that data and export it out
to an external txt file.
 
I have done it in vba only because I do not know pure vb (and don't own it).
There's no requirement to change it as it does the job - just need it
automated. They are running Windows NT. You lost me on the NT service OCX.
What is that?
 
Rgds
Kath

----- Original Message ----- 
From: Drew  <mailto:DWUTKA at marlow.com> Wutka 
To: 'AccessD at databaseadvisors.com  <mailto:'AccessD at databaseadvisors.com '>
' 
Sent: Friday, May 09, 2003 5:25 PM
Subject: RE: [AccessD] Scheduling an mdb to run using AT

What are you trying to run.  Is it just a data routine, or is it running
reports?  If it's just a data routine, I personally recommend using the NT
service OCX, which allows a VB .exe to run as an NT service.  Much easier to
deal with, shows up in the list of services, the ocx has an easy method to
dump information in the event viewer, etc.

Running reports can be done this way too, but it needs to use Automation.  

>From what I understand, VB.Net has the NT Service capability built in.

Drew

-----Original Message-----
From: Software Design & Solutions Pty Ltd.
To: AccessD at databaseadvisors.com <mailto:AccessD at databaseadvisors.com> 
Sent: 5/8/03 10:08 PM
Subject: [AccessD] Scheduling an mdb to run using AT

Have any of you had much experience with scheduling applications to run
(ie. mdb files) using the AT command?
 
I am trying to get a job to run overnight for a client using the
following syntax:
 
at 14:26 /interactive /Every:M,T,W,Th,F cmd /c D:\Prices\Priceload.bat
 
where the files Priceload.bat contains the following:
  _____  

@ECHO OFF
REM Daily Price File Load
TITLE GBST PRICE LOAD
 
M:
cd \Price
echo ENTER PRICE FOLDER
ntsleep 2 > nul
 
Call Price.mdb

  _____  

 
I then get the message 'M:\Price\Price.mdb file not found'.
 
Because it is real PITN to keep mucking around with this syntax in DOS,
I am also having a play with some shareware(?) the client had called
WINAT. It seems good, but when I use it at my client site to edit the
paremeters of the AT command, extra characters appear at the end of the
command, so I am not sure whether the command will work or not.
Characters are things like pipes and @symbols. 
 
So my question for anyone using AT is: do you have any tips to share?
What is the most reliable way you have found to schedule an mdb to run?
 
TIA
Kath
 
 
Kath Pelletti
Software Design & Solutions Pty Ltd.
Ph: 9505-6714
Fax: 9505-6430
SDSSoftware at Optusnet.com.au <mailto:SDSSoftware at Optusnet.com.au>  <
mailto:SDSSoftware at Optusnet.com.au <mailto:SDSSoftware at Optusnet.com.au> > 
 <<ATT11462.txt>> 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com <mailto:AccessD at databaseadvisors.com> 
http://databaseadvisors.com/mailman/listinfo/accessd
<http://databaseadvisors.com/mailman/listinfo/accessd> 
Website: http://www.databaseadvisors.com <http://www.databaseadvisors.com> 




  _____  




_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030513/1910888b/attachment-0001.html>


More information about the AccessD mailing list