[AccessD] Macro vs VBA

> 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