[AccessD] Macro vs VBA

Maybe the program could email someone when the process fails.

Scott Marcus
Computer Programmer
TSS Technologies Inc.
www.tss.com
513-772-7000 x1113


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte
Sent: Thursday, April 20, 2006 11:14 AM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Macro vs VBA

I agree...but the dilema would be how to notify someone.
>But I think nobody can be 100% sure about that - therefore use VBA and
>program graceful user friendly messages for

The database will be opened once a day by a scheduler...there wouldn't
be 
anyone there to see the userfriendly message.  any suggestions?

Thanks,

Mark


>From: "Shamil Salakhetdinov" <shamil at users.mns.ru>
>Reply-To: Access Developers discussion and problem 
>solving<accessd at databaseadvisors.com>
>To: "Access Developers discussion and problem 
>solving"<accessd at databaseadvisors.com>
>Subject: Re: [AccessD] Macro vs VBA
>Date: Thu, 20 Apr 2006 18:57:16 +0400
>
> > P.S...Its funny how the simple projects bring more questions...
>Mark,
>
>The more questions you ask(yourself) and answer(by yourself) the
simpler 
>you
>project will look like in the end...  :)
>
>If you're 100% sure that your queries will never break because of lost
>connections to Informix or "dirty" source data etc. - go with macros...
>
>But I think nobody can be 100% sure about that - therefore use VBA and
>program graceful user friendly messages for all the exceptional cases
you
>can imagine and for the ones you can't imagine/foresee now program
error
>handling.
>
>This is what VBA gives - "bullet-proof' solutions and customers'
>satisfaction...
>
>Shamil
>
>----- Original Message -----
>From: "Mark A Matte" <markamatte at hotmail.com>
>To: <accessd at databaseadvisors.com>
>Sent: Thursday, April 20, 2006 6:15 PM
>Subject: [AccessD] Macro vs VBA
>
>
> > Hello All,
> >
> > Some one contacted me with an app that links to an mdb that links
via 
>odbc
> > to informix(I think)...anyway...I'm going to put a few queries
together
> > that
> > create a local copy of the data...delete the old...that kinda stuff.
No
> > big
> > deal...this mdb will do nothing else than house a temp recordset.
the 
>mdb
> > will be running 1 append and 2 delete queries...once a day via a
> > scheduler.
> > My question is is there any difference, benefit, concern, or
anything to
> > think about when choosing between launching these 3 queries with a
macro
> > or
> > VBA?
> >
> > Thanks,
> >
> > Mark
> >
> > P.S...Its funny how the simple projects bring more questions...
> >
> >
> > --
> > 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


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





NOTICE:  This electronic mail transmission is for the use of the named individual or entity to which it is directed and may contain information that is privileged or confidential.  If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of any information contained herein is prohibited.  If you have received this electronic mail transmission in error, delete it from your system without copying or forwarding it, and notify the sender of the error by replying via email or calling TSS Technologies at (513) 772-7000, so that our address record can be corrected.  Any information included in this email is provided on an “as is” and “where as” basis, and TSS Technologies makes no representations or warranties of any kind with respect to the completeness or accuracy of the information contained in this email.