[AccessD] Moving from Access to web???

Mark,

If you use SQL server you can create a stored procedure that does the bulk
of the work and schedule a job if you want it to run at certain intervals or
have a button or trigger on the web page if you want to run it on demand.

String concatenation is not one of VB's strengths and in fact it will be the
bottleneck so you might want to consider VB.NET with its StringBuilder class
to do all that hard work for that part.

When you transfer the process to a server-based app you will have to contend
with dealing with a mail server and you will experience timeouts when you
use the CDO mail components for large volumes of mail as opposed to using
Outlook automation to process the emails.

Eric

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark A Matte
Sent: Thursday, August 16, 2007 10:13 AM
To: accessd at databaseadvisors.com
Subject: [AccessD] Moving from Access to web???

Hello All,

Since we're on the topic of the web...my most recent post was related to SQL
speed...and everything so far has been built in access.

In making this service available to online...I really don't know how to do
this.  Currently VBA is doing all of the work.  Looping through recordsets
and running queries.  I use a form timer to launch it.

If I leave it in Access...does this mean the MDB is always open on the
hosting server?

If I put it in SQL Server...what does the looping through results?

I'm just confused again...lol

In a nutshell...
I run 10K queries against  4K records...and for each query I concantenate
the results...and email them out.  I can create the webpage for people to
sign up...but I need suggestions on what to use to 'do' the stuff that VBA
is currently doing behind the scenes?

Thanks Again,

Mark A. Matte