[AccessD] Ten most common tasks/problems in Access

Hi Stuart,

Do you have the declare statement you would include in Access for the DLL and a sample call?  I've used the .Exe in the past but would rather not have to shell out to run it if I can use the DLL references.  I couldn't find the info on the yahoo board nor in the blat Zip file (just updated a few days ago) so if you get a chance and can dig up the info, that would be much appreciated.

Thanks,

John



---
John Bodin



________________________________________
From: accessd-bounces at databaseadvisors.com <accessd-bounces at databaseadvisors.com> on behalf of Stuart McLachlan <stuart at lexacorp.com.pg>
Sent: Sunday, October 19, 2014 5:22 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Ten most common tasks/problems in Access

1. It's not a COM object with a complicated object model, it's just uses simple command
string.
2. It doesn't have any dependencies or installation requirements
3. It doesn't rely on the presence of other software.
4. It doesn't rely on MAPI.

Just drop a  single 120KB DLL somewhere, include a single Declare statement in your code.
Then build a command string and send it as a single parameter to declared Blat function.


--
Stuart


On 20 Oct 2014 at 6:05, David Emerson wrote:

> Hi Stuart,
>
> How does it differ from using cdosys.dll?
>
> Regards
>
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart
> McLachlan Sent: Monday, 20 October 2014 12:48 a.m. To: Access
> Developers discussion and problem solving Subject: Re: [AccessD] Ten
> most common tasks/problems in Access
>
> Yep with PB  you can build "industry standard" DLLs  exactly the same
> as those created with C, C++, C#, MASM etc.   No need to "register"
> them or to have any fancy installation procedure - just copy to a
> suitable location and use them.
>
> Blat does not depend on a specific (or any) email client and does not
> rely on the identity of the logged in user - so you can use it to
> automate emails from any address you want running scheduled tasks on a
> server for example, even if there is no email client installed on the
> machine.    I've used it in some organisations that don't use
> Outlook/Exchange at all.
>
>
> --
> Stuart
>
>
> On 19 Oct 2014 at 7:29, Arthur Fuller wrote:
>
> > Thanks, Stuart. I'll add these to my list. I haven't ever written a
> > DLL, and until now was under the obviously mistaken impression that
> > you had to write them in C++ or C#. I didn't know you could do it in
> > Power Basic.
> >
> > I have heard of blat but know nothing about it. What does it give
> > you that other emailers don't? (I.e. why did you choose it against,
> > say, integration with Outlook?)
> >
> > Arthur
> >
>
> --
> 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