[AccessD] Retrieve command line arguments

Rocky Smolin at Beach Access Software rockysmolin at bchacc.com
Fri Jan 25 09:58:54 CST 2008


Max:

That would work except that the function I need to run is embedded in the
application and the client does not want a separate mdb or mde just to run
that function - has to be in embedded in the whole application.  Users -
gotta love 'em.

Rocky
 




 	
	

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Friday, January 25, 2008 7:54 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Retrieve command line arguments

Rocky,
We do this every night.
Just call the app from Windows Scheduler.
We use the autoexec macro to call a function which runs whatever and then
closes down.

You could have the Startup Options set to a form which immediately calls the
function also and then closes down.

You don't need any command line parameters.

Max
Ps. If you wanted to lock the app down, make it a MDE instead of a MDB +
password protection of the database. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin at
Beach Access Software
Sent: Friday, January 25, 2008 3:34 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Retrieve command line arguments

Gary:

That would be my preferred design.  But the client wants it this way. 

Rocky



 	
	

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gary Kjos
Sent: Friday, January 25, 2008 7:22 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Retrieve command line arguments

Does it HAVE TO be in the same database?  How about a seperate database that
links to the same tables in the original and then when you open that
"Automail" database it runs and sends the reports and then exits.

GK

On 1/25/08, Rocky Smolin at Beach Access Software <rockysmolin at bchacc.com>
wrote:
>
> Dear List:
>
> I want to run a function in an application (emails out reports) 
> automatically.  I see that one way to do this is to use the /x switch 
> on startup to run a macro which will run a module which could have 
> Application.Quit at the end of it.  But I can't seem to get this to work.
> And besides, I'm under the impression that macros are not PC anymore.
>
> Anyway, if I can 'see' the startup switches on the command line that 
> calls access and starts the app,  I suppose I could intercept al the 
> startup housekeeping, run the reports, send the emails and exit.
>
> Is there a way to see what the command was that started an app , IOW 
> retrieve the command line arguments ?  Or is there a better way to do
this?
>
>
> The automated email sender has to be part of the larger app - 
> originally it was split off for development purposes, but now, it's 
> part of the design that it should be integrated into the application.
>
> MTIA
>
> Rocky
>
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


--
Gary Kjos
garykjos at gmail.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.19.11/1242 - Release Date: 1/24/2008
8:32 PM
 

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

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

No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.19.11/1242 - Release Date: 1/24/2008
8:32 PM
 




More information about the AccessD mailing list