[AccessD] Macro vs VBA

Implement unattended execution mode and logging.
Then port your solution by copy&paste to VB6.
Abandon MS Access.
Make VB6 GUI-less/console .exe app.

Shamil

----- Original Message ----- 
From: "Mark A Matte" <markamatte at hotmail.com>
To: <accessd at databaseadvisors.com>
Sent: Thursday, April 20, 2006 7:14 PM
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
<<< tail skipped >>>