We are on the verge of acquiring a new win3k system for local asp testing
development purposes and to allow satellite branches to ftp-in and grab
images.
I need to utilize the bulk emailing facility to send up to 20,000 emails a
day after looping through my customer list which resides in a Access
database.
My current web host restricts me to 800 emails today while our 3rd party
email bulk broadcaster will not allow my to acccess their API to send the
email.
I am technically challenged when iut comes to OS pecularities and need a
simple, elegant solution to bulk emailing fast - any feedback welcome.
- Jason
Thank you. I hope this information is helpful.
Tim Coffey [MSFT]
This posting is provided “AS IS” with no warranties, and confers no rights. You assume all risk for your use. © 2001 Microsoft
Corporation. All rights reserved.
--------------------
| Reply-To: "jason" <ja...@catamaranco.com>
| From: "jason" <ja...@catamaranco.com>
| Subject: Bulk emailing :: local smtp collab with asp cdo and Access 2000?
| Date: Mon, 25 Aug 2003 16:19:40 -0400
| Lines: 21
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
| Message-ID: <Ow349Y0a...@TK2MSFTNGP09.phx.gbl>
| Newsgroups: microsoft.public.inetserver.iis
| NNTP-Posting-Host: wkstn19.catamarans.com 205.197.3.211
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.inetserver.iis:272319
| X-Tomcat-NG: microsoft.public.inetserver.iis
MDAC and Jet 4.0 are installed by Windows 98 Second Edition, Me, 2000 and
XP, including the Jet 4.0 OLEDB provider.
My understanding was that OLEDB and ADO were designed to provide a
thread-safe database architecture that can be used, for example, on a web
server by ASPs.
Now you are saying that Jet is not thread safe and is not recommended in a
web environment. I don't understand. Should I not use the Jet OLEDB provider
in an ASP? Is there some sort of thread synchronization built in that I
should know about?
Paul
"Tim Coffey" <tim...@online.microsoft.com> wrote in message
news:A2HnIJfc...@cpmsftngxa06.phx.gbl...
I appreciate your feedback - as this is a difficult route for me.
I just wanted to confirm that you are saying it is possible for me to send
out "20,000" emails per day via the local smtp component configured in
win2003 server, although Access may not be robust enough to be used as the
data source.
But, can you clarify:
1. I have been told that local smtp is only SINGLE-THREADED which means it
cannot handle mutlipe send-outs to various email addresses at the same time.
IN other words, it does it one at a time.
2. I spoke to a 3rd party add on software developer for Act! Contact
Managements systems who built E-blast the mass mailing facility for Act! who
says I am possibly asking for trouble. He uses something called "STMP
EXPRESS" which is apparently a multi-threaded stmp component which can
handle up to 80 concurrent threads. He says this is actually what MS and
other big companies use and he purchased a distributable license to enable
insertion in his programs.....have you heard about this com - is it easily
available? What are your throughts on the local smtp restrictions ....can
you actually send out this many emails?
3. Our domain (@catamarans.com) is sitting with our remote web host who
maintains our primary company mail server. Will I need the domain on our
internal server to ensure the success of any email campaign via local smpt
in light of stricter server validation on recipicient servers (eg checking
for reverse dns; checking for domain validity etc) I do not fully understand
these issues and wonder if a bulk email compaign from a local server is
doomed for failure if one does not also host the domain. I am only
considering local bulk emailing due to web host limits.
Appreciate further feedback to my long-winded summary above :)
- Jason
ps: I have investigated FMSinc.com MASS EMAILER FOR ACCESS which uses local
smtp - have you had any experience with the success or failure of this
product?
"Tim Coffey" <tim...@online.microsoft.com> wrote in message
news:<A2HnIJfc...@cpmsftngxa06.phx.gbl>...
> SMTP works just fine for what you want. Although access dbs are not
> microsoft.public.inetserver.iis.smtp_nntp
>
>
> Tim Coffey [MSFT]
>
> Corporation. All rights reserved.
> --------------------
> | Reply-To: "jason" <ja...@catamaranco.com>
> | From: "jason" <ja...@catamaranco.com>
> | Lines: 21
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | Message-ID: <Ow349Y0a...@TK2MSFTNGP09.phx.gbl>
> | Newsgroups: microsoft.public.inetserver.iis
> | NNTP-Posting-Host: wkstn19.catamarans.com 205.197.3.211
> | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
> | Xref: cpmsftngxa06.phx.gbl microsoft.public.inetserver.iis:272319
> | X-Tomcat-NG: microsoft.public.inetserver.iis
> |
> |
> | images.
> |
> | database.
> |
> | email.
> |
> |
> | - Jason
> |
> |
> |
>
>
Tim,
I appreciate your feedback - as this is a difficult route for me.
I just wanted to confirm that you are saying it is possible for me to send
out "20,000" emails per day via the local smtp component configured in
win2003 server, although Access may not be robust enough to be used as the
data source.
But, can you clarify:
1. I have been told that local smtp is only SINGLE-THREADED which means it
cannot handle mutlipe send-outs to various email addresses at the same time.
IN other words, it does it one at a time.
2. I spoke to a 3rd party add on software developer for Act! Contact
Managements systems who built E-blast the mass mailing facility for Act! who
says I am possibly asking for trouble. He uses something called "STMP
EXPRESS" which is apparently a multi-threaded stmp component which can
handle up to 80 concurrent threads. He says this is actually what MS and
other big companies use and he purchased a distributable license to enable
insertion in his programs.....have you heard about this com - is it easily
available? What are your throughts on the local smtp restrictions ....can
you actually send out this many emails?
3. Our domain (@catamarans.com) is sitting with our remote web host who
maintains our primary company mail server. Will I need the domain on our
internal server to ensure the success of any email campaign via local smpt
in light of stricter server validation on recipicient servers (eg checking
for reverse dns; checking for domain validity etc) I do not fully understand
these issues and wonder if a bulk email compaign from a local server is
doomed for failure if one does not also host the domain. I am only
considering local bulk emailing due to web host limits.
Appreciate further feedback to my long-winded summary above :)
- Jason
ps: I have investigated FMSinc.com MASS EMAILER FOR ACCESS which uses local
smtp - have you had any experience with the success or failure of this
product?
"Tim Coffey" <tim...@online.microsoft.com> wrote in message
news:<A2HnIJfc...@cpmsftngxa06.phx.gbl>...
> SMTP works just fine for what you want. Although access dbs are not
For more specific questions on using Access, try here: microsoft.public.inetsever.asp.db They can give you all the ins and outs.
Thank you. I hope this information is helpful.
Tim Coffey [MSFT]
This posting is provided “AS IS” with no warranties, and confers no rights. You assume all risk for your use. © 2001 Microsoft
Corporation. All rights reserved.
--------------------
| From: "Paul Baker" <ask>
| References: <Ow349Y0a...@TK2MSFTNGP09.phx.gbl> <A2HnIJfc...@cpmsftngxa06.phx.gbl>
| Subject: Re: Bulk emailing :: local smtp collab with asp cdo and Access 2000?
| Date: Wed, 3 Sep 2003 08:41:42 -0400
| Lines: 79
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <eDSR7ihc...@TK2MSFTNGP12.phx.gbl>
| Newsgroups: microsoft.public.inetserver.iis
| NNTP-Posting-Host: 66-192-38-10.bccsoftware.com 66.192.38.10
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.inetserver.iis:273624
| X-Tomcat-NG: microsoft.public.inetserver.iis
Thank you. I hope this information is helpful.
Tim Coffey [MSFT]
This posting is provided “AS IS” with no warranties, and confers no rights. You assume all risk for your use. © 2001 Microsoft
Corporation. All rights reserved.
--------------------
| Reply-To: "jason" <ja...@catamaranco.com>
| From: "jason" <ja...@catamaranco.com>
| References: <Ow349Y0a...@TK2MSFTNGP09.phx.gbl> <A2HnIJfc...@cpmsftngxa06.phx.gbl>
| Subject: Re: Bulk emailing :: local smtp collab with asp cdo and Access 2000?
| Date: Wed, 3 Sep 2003 11:11:05 -0400
| Lines: 312
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 5.50.4522.1200
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
| Message-ID: <uvvRg2ic...@TK2MSFTNGP11.phx.gbl>
| Newsgroups: microsoft.public.inetserver.iis
| NNTP-Posting-Host: wkstn19.catamarans.com 205.197.3.211
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.inetserver.iis:273647
| X-Tomcat-NG: microsoft.public.inetserver.iis
I don't care enough to ask questions about it. It's one of those things I
just expect to work. I don't see it documented anywhere that it does not. I
have never seen a problem.
I use the Jet 4.0 OLE DB provider on an internal web server to query a
simple database, but not on a production web server.
Paul
"Tim Coffey" <tim...@online.microsoft.com> wrote in message
news:kIFksNoc...@cpmsftngxa06.phx.gbl...
Why don't you just try it, instead of theorising?
Paul
"Tim Coffey" <tim...@online.microsoft.com> wrote in message
news:VPsOROoc...@cpmsftngxa06.phx.gbl...
Thank you for your interest in our Total Access Emailer program
(http://www.fmsinc.com/products/Emailer/index.asp).
Please let me assure you that the program works well and will send the
quantities of emails you're seeking through your SMTP server. If your
ISP won't be your SMTP server, you can use your own (part of Win2K or
later). We've seen it send tens of thousands of emails per hour
(depends how large your message is, bandwidth, etc.)
I've read several of your threads and it appears you're rather
concerned about whether this (or any) FMS product will work for you.
Please let me reassure you that your satisfaction is very important to
us. The free demo lets you send emails up to 100 at a time, so you
can test the system for free to see if its features meet your needs.
If you decide to get the shipping version, you'll be able to send an
unlimited number of emails at one time, and you'll get the
programmatic interface which would allow you to add it to a button in
your Access application.
All our products come with a 30 day money back guarantee, so it should
be a risk free experience for you. Beyond that, I'm personally
interested in making sure we exceed each of our customer's
expectations. As our 12th commercial Access product, Total Access
Emailer represents some of the best Access skills in the world. We
know what we're doing and are the leading Access 3rd party firm
because we've created great products and treated our customers well.
We want you to be happy.
Finally, I was the lead designer and one of the primary authors of
Total Access Emailer, so I'm particularly keen to make sure you're
happy. We already have many Total Access Emailer customers who are
quite amazed how it simplified their email needs. It will let you
spend time thinking about the emails you need to send rather than how
to send them.
FYI, we use Total Access Emailer for our own emails too. There's
nothing like having developers eating their own dog food to reassure
you that a product works. We hope you give us a try.
Luke Chung
President
FMS, Inc.
http://www.fmsinc.com
"jason" <ja...@catamaranco.com> wrote in message news:<uvvRg2ic...@TK2MSFTNGP11.phx.gbl>...
So Total Access Emailer does not include an SMTP server. You would be using
someone else's SMTP server, and looking at Microsoft's SMTP server just as
we discussed.
Don't waste your money on what sounds like a glorified email client. You can
use CDO for Windows 2000 to get the same effect. In fact, it probably does
the same.
Paul
"Luke Chung" <Luket...@yahoo.com> wrote in message
news:735b418b.03090...@posting.google.com...
I do not yet have access to a local server to send bulk emails up to 8000
per day. I would have to combine CDO, asp on my local win2k smtp to solve
this problem.
Further - and this is big - my current customer/pagewatch database is online
at my web host where it collects new form driven customers and connects them
to the boats they are interested in.
I would thus have to institute some download mechanism to get the updated
online access database onto my machine and then active CDO either via WSH or
via a task scheduler which calles the local CDO web page script to cycle
through the list (8000).
Its easy to say just go ahead and do it but there are multiple problems:
1. How do I effectively test against the 8000 without pissing them off for
spam
2. How much pressure will create on my machine
3. How will I ascertain the success of the mailings
4. How do I handle the undeliverables.
5. How do I handle the fact that our principle domain eg .catmararans.com
will not reside on my local machine thus creating potential flags for
recipient servers who now days want to make sure of the server/domain
alliance
This application is very time sensitive with regards daily send outs and I
will get the brunt of a huge whipping if this goes wrong.
Further, I am still trying to work out if ASPEmail OR Cdo SEND.QUEUE is the
best route.
I do not believe in just trying things when I can work out in advance what
the curve balls and possible better solutions could be. This saves time in
the long run and leads to more creative solutions.
FMS email seems like a potential choice as it is already buitl on top of
Access. I could thus maybe integrate my existing comparison queries to check
for boat changes and then assmble the dynamic mailing list for those
particular boats and somehow pull that into fms mailer - I am still not
convinced.
I have this headache of trying to synchronize with an online access database
which is doing all the work. I cannot simply download and re-upload etc as I
will then
be overwriting data.
I mentione SMTP Express from quick pro as it seems to offer advanced
handling as well as performance benefits (multithreaded). I have been told
repeatedly in the ASP newsgroups that as soon as you go over 800 emails per
day you should really go for a list server (ignoring the costs and
complexity of doing so).
I need this application to work the first time as I really don't feel like a
debugging and undeliverable or spamming bloodbath even though our mailings
are legitimate.
- Jason
"Paul Baker" <ask> wrote in message
news:uY2EIeg...@TK2MSFTNGP11.phx.gbl...
I will try to answer each of your questions.
1. Combining ASP, CDO and Windows SMTP server sounds like a great idea. To
avoid pissing them off, don't test it with your SMTP host's server. Instead,
test it with your local Windows 2000 SMTP server. If you still do not have
access to such a server, get it! All you need is Windows 2000 Professional
(not server). You could have it up and running in a day a cost that is low
enough to easily be justifiable considering the business you could generate.
2. This is not a reason to avoid going ahead and trying it. Try it and you
can observe how much pressure it will create.
3. Send the mailings to people you know or multiple copies to yourself.
Testing things like this does not require the large numbers you describe. If
the emails are successfully received when you sent them to a handful of
people you know or yourself, there is no reason to believe why they wouldn't
be successful in larger numbers. Most likely, if the SMTP server did have a
problem, what would happens is that there would be an error message or the
queue would grow and messages would be delayed. It wouldn't just
mysteriously lose the emails.
4. Just let them bounce for now. Eventually, you might want to look at ways
to trim the mail box or remove consistently bouncing addresses from the
list, but I wouldn't worry about it now.
5. I have never seen such things enforced. Spoofing is as rampant as ever. I
doubt I will in the future, as an apparent mismatch between the sender
domain and the SMTP server domain is not contrary to any specification, so
far as I know, therefore must be respected. In the short term, I would not
worry about it. In the long term, I would look at hosting your own domain
and web server.
Beware that much third party software just re-uses CDO or Windows SMTP
server and wraps it in a pretty UI.
I don't know what else I can do to help if you're unwilling to try it
without knowing the outcome of every single detail in advance. I just don't
know those details.
Paul
"jason" <ja...@catamaranco.com> wrote in message
news:%23%237YLoud...@TK2MSFTNGP11.phx.gbl...
All you need is Windows 2000 Professional
> (not server). You could have it up and running in a day a cost that is low
> enough to easily be justifiable considering the business you could
generate.
This is my present OS. So this can be done.
2.. Most likely, if the SMTP server did have a
> problem, what would happens is that there would be an error message or the
> queue would grow and messages would be delayed. It wouldn't just
> mysteriously lose the emails.
Could you expand on this. I have not actually used sendToqueue with regards
CDO and I am actually
not sure how to phrase the code to:
A. loop my db and capture the mulitple emails into the BCC list
B. Error handling. Can you actually trap any outbound or inbound errors
with regards the success of the outgoing email - this seems mysterious to
me.
Or is the purely the result of some BAD_EMAIL folder that sits in IIS or
ones outlook inbox.
> 4. Just let them bounce for now. Eventually, you might want to look at
ways
> to trim the mail box or remove consistently bouncing addresses from the
> list, but I wouldn't worry about it now.
This sounds easy but I am really unsure of the actual steps.
- Do you merely assign a bounce email address eg: bou...@myserver.com which
comes
back into your inbox. Or do you somehow catch these inside IIS? I take it an
undeliverable
is the same as a bounce as I have heard others refer to these as 'soft' and
'hard' bounces?
> 5SPOOFING....In the short term, I would not
> worry about it. In the long term, I would look at hosting your own domain
> and web server.
Ok - this sounds logical.
> Beware that much third party software just re-uses CDO or Windows SMTP
> server and wraps it in a pretty UI.
Ok - but what about the facts presented by Quiksoft and others which
ascertains that local smtp via eg: win2k pro if not actually
multithreaded but single threaded and can only do one email at a time in
queue while their components can handle multipe sendouts
(eg 64 at a time) to make your mailing more performance and time effecient -
I am struggling to see how local smtp can compete against
the claim.
> I don't know what else I can do to help if you're unwilling to try it
> without knowing the outcome of every single detail in advance. I just
don't
> know those details.
>
You have been very helpful! One last hurdle: Have you actually looped
through an access 2000 database and retrieved
8000 customer records on the fly. And further, bear in mind, the email has
to be constructed dynamically and is determined
by daily changes to the boat description and what website visitors have
subscribed to the particular boat. I have to compile
a summary for each of those 8000 and then send out on the fly.....can you
offer any advice on this especially if my database
resides with my web host and I first have to download to local win2k server
to undertake the mass loop.
Many thanks for your time.
Jason
Expanding upon 2:
You can trap error using "On Error Resume Next". However, these will just be
things like the SMTP server is not responding because it is down. If you are
configuring CDO to use the local drop directory, you won't even get that
error.
CDO will generate errors for things like you did not specify From or Sender.
But this would be a bug in your code that you could fix.
CDO will not generate an error once it is in the local drop directory or
sent to an SMTP server. You can then go on to send other emails. As you
probably know, after that point various things can happen to the email, but
this is not the concern of the client. The sender will generally get a fail
report back.
For exact error handling techniques, you'll just have to experiment a bit.
Clarification on 4:
The sender gets any fail reports, eg. if the recipient's mail server is
unreachable, does not recognize the user or the user's mail box is full. You
specify the sender using the Sender property when you send the mail, so
there you go.
As I said above, the client is out of it at that point and will not generate
errors in these types of cases.
You act like you never sent an email and had it bounce before??
Regarding SMTP server issues:
Sending your email to a SMTP server on another machine will take a bit
longer than putting the email in the local drop directory, as it has to
actually communicate using SMTP, but given that you have an average of 10
seconds per email, you should easily have enough time on your hands.
The looping through the Access database should be very simple and efficient.
There was one claim about the Windows SMTP server being single-threaded, but
you'll notice that noone followed up to agree, noone provided any
documentary evidence and noone from Microsoft commented.
I am going to go out on a limb and say that I think it is multi-threaded.
Why wouldn't it be? Just try dumping a whole bunch of emails in there and
see whether the number of threads grows. Or see if all emails queued after
one that is destined for a machine with no SMTP server on it are held up
until it figures out that the SMTP server is not going to respond.
Paul
"jason" <ja...@catamaranco.com> wrote in message
news:unIyUQwd...@tk2msftngp13.phx.gbl...
This KB article seems to suggest that it is multi-threaded, but that proper
configuration may be necessary.
http://support.microsoft.com/default.aspx?scid=kb;en-us;264891
Paul
Simply download a demo of our Total Access Emailer program and see if
it works for you (http://www.fmsinc.com/products/Emailer/conftrial.asp).
You'll be able to go against your live data to generate the email
blast. If you want to get fancy, you can reference fields in your
messages to customize each email. The trial is limited to 50 email
records in your table. The shipping version doesn't have a limit and
also lets you use queries.
You already have an SMTP server in your OS, so you're ready to go.
Good luck.
Luke
"jason" <ja...@catamaranco.com> wrote in message news:<##7YLoudD...@TK2MSFTNGP11.phx.gbl>...
I assure you that Total Access Emailer is a lot more than a
"glorified" email client.
Many Access users and developers have found it quite valuable for
meeting their email blast challenges. The features and functionality
of Total Access Emailer cannot be replicated without a great deal of
coding in Access.
Luke Chung
President
http://www.fmsinc.com
"Paul Baker" <ask> wrote in message news:<uY2EIeg...@TK2MSFTNGP11.phx.gbl>...
I'll agree that it's functionality cannot be replicated without a great deal
of coding in Access. I can see that it has a wide range of functions from
your web site.
However, your implication is that a great deal of coding in Access would in
fact produce similar results. All that does is lend credence to my
suspicions:
1. You can't write an SMTP server in Access. Therefore, I suspect your
product does not have its own SMTP server. Jasons concerns were largely
about the peformance of the SMTP server. If your product does not include an
SMTP server or includes one that can boast no advantage over Microsoft's,
your product won't help him there.
2. Access cannot do much that is not database-related without using VBA, ie.
COM. Therefore, I suspect your product uses CDO. CDO is simple to use from
his ASP.
I have no doubt that your product is valuable and has its place. I just
don't think it would help Jason much, from what I've heard.
Paul
"Luke Chung" <Luket...@yahoo.com> wrote in message
news:735b418b.03090...@posting.google.com...
I also uncovered another potential obstacle in the smtp_nntp group.
Apparently - If I wish to customize content for each subscriber on my list I
will not be able to use the BCC field.....
In other words - IF I decide to send out a mass broadcast in one go I need
to have ONE email template; If I want to customzie the content I have to
send MANY emails to the same person (ie boats that have changed) to allow
customization of content....
Very confusing!
- Jason
"Paul Baker" <ask> wrote in message
news:e6qkGzxd...@tk2msftngp13.phx.gbl...
Yes, actually another newsgroup is probably a better place for most of this.
But I am glad to help anyway I can.
Don't use the IIS built-in email thingy (I can't even find the darn thing
now in MMC). Just use CDO. It's very simple anda a more direct route. You
will have more control. You can specify either an SMTP account on a specific
server or you can specify that it should use the local drop directory. Read
about this in CDO.Configuration documentation.
You *can* use the BCC field, but not in the way you're thinking.
Each mail message obviously only has one body. If the body is constant, you
can send one message. Generally, you would use the BCC field. If the body is
variable, you must send one message for each recipient. Generally you would
use the To field. I just use the VBScript function Replace to do customize
the body.
Paul
"jason" <ja...@catamaranco.com> wrote in message
news:uuVU%23x6dD...@TK2MSFTNGP11.phx.gbl...
So:
Thus,
1. I cycle the customer table (eg First record - Person A)
2. See what boats they are watching ie Person A
3. Cycle the boats table to see if there any changes (eg: Boats 1, 2, 3
have changed)
4. If yes I dynamically build the content for Person A listings all the
changes for Boat 1, 2, 3
5. Send Email to him in TO address
6. Move to next record Person B in my database loop
7. Goto Step 2 and repeat process
That should work right?
- Jason
"Paul Baker" <ask> wrote in message
news:u5XMQS7d...@TK2MSFTNGP11.phx.gbl...
That's right. You would be sending separate emails to each recipient so
there is no connection between them.
It seems to me that you are getting so bogged down with the programming
details that you're not thinking about the behaviour of emails that you are
already used to. If you were to do this thing manually, you would send
separate emails to each person with one name in the To field too. All you're
doing is automating it.
Paul
"jason" <ja...@catamaranco.com> wrote in message
news:%23uKN8C9...@TK2MSFTNGP10.phx.gbl...
I guess the last remaing question is if there is a further way to decrease
the load by somehow pre-assembling the emails according to the watched item
rather than first cycling the customer-boats table to see which customers
are watching what and then go to find out of if those watched items have
changed?
You have been an immense help - thanks!
- Jason
"Paul Baker" <ask> wrote in message
news:ecGFk25d...@TK2MSFTNGP12.phx.gbl...
I am still evaluating your product - it has seem really great features - I
just wish there were a few more programming examples than the two starter
examples in your help file.
Cheers
Jason
"Luke Chung" <Luket...@yahoo.com> wrote in message
news:735b418b.03090...@posting.google.com...
Without knowing the specifics of your operation, I don't know. But probably.
Paul
"jason" <ja...@catamaranco.com> wrote in message
news:uqV0iyVe...@TK2MSFTNGP10.phx.gbl...