[AccessD] Access Reporting Application - Dealing with Excel InputFiles that are E-mailed Daily

That's what I'd do.

Just rename whatever is in that folder using VBA as the first step of your processing.
Then process it as at present.  You don't have to manually rename it.

How to get that file into the subfolder is the key.  That depends on your email setup. If your 
mail comes through a local server, then a server based rule would be the answer.  If not, 
then you will need an Outlook rule to save the attachment based on originator/subject or 
whatever.


On 16 Apr 2013 at 22:09, James Button wrote:

> Put the file in subfolder \newin\ of the folder where you store the 
> processed data and
> nightly?, process all the files in that subfolder
> (in ascending datetime sequence) and have the processing,
> or data extraction script move them up a level.
> 
> JimB
> 
> ----- Original Message ----- 
> From: "Brad Marks" <BradM at blackforestltd.com>
> To: "Access Developers discussion and problem solving" 
> <accessd at databaseadvisors.com>
> Sent: Tuesday, April 16, 2013 9:32 PM
> Subject: [AccessD] Access Reporting Application - Dealing with Excel 
> InputFiles that are E-mailed Daily
> 
> 
> > All,
> >
> > We have an Access 2007 application that automatically generates and
> > e-mails reports every night.  This application is primarily pulling data
> > from a SQL Server database via ODBC.  It has worked nicely for about 3
> > years.
> >
> > Recently, an enhancement was made to the application which requires the
> > pulling of a small amount of data from an Excel file.  This new feature
> > seems to also be working nicely.
> >
> > Each day, a new Excel file is e-mailed to me.  I DO NOT have control
> > over how this file is named.  When I receive the e-mail, I save the
> > attached Excel file with a consistent name so that the nightly Access
> > application can find it.  In other words, I save the Excel file with the
> > name that the Access application is expecting to find.  This procedure
> > works, but it does require manual intervention every day.  I would like
> > to find a better method so that this manual intervention is not
> > required.
> >
> > Has anyone else ever run into this type of situation?
> >
> > I have started to experiment with Outlook VBA code.  I have written
> > quite a bit of Access VBA, but not much Outlook VBA.  I am not sure of
> > the potential of this route.
> >
> > Any ideas or insights would be appreciated.
> >
> > Thanks,
> > Brad
> >
> > -- 
> > 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
>