[AccessD] Terrible performance like I have never seen before

Thanks for the input, Gustav.  I was assuming that I ODBC was a complete
no-no.  It would be tempting to start with ODBC and then work towards Jim's
approach.  Of the 300 or so forms in my big apps, probably 10 to 20 are
crucial and need to be as fast as possible.

One of the main reasons that I want to get going on converting from Access
is that I'm planning on retiring in the next couple of years and don't want
to leave my clients stuck.  It's a lot easier to find Visual Studio
programmers than Access programmers with sufficient knowledge.

By the way, one of my clients lost his Access 2003 install disks last week
and bought Office 2010.  My 2003 database went CRASH, BANG, !&%%!

Doug

On Thu, Jul 8, 2010 at 9:29 AM, Gustav Brock <Gustav at cactus.dk> wrote:

> Hi Doug
>
> Not to spoil the party neither the bill to the client ... but you could -
> as a first attempt - try to run the upsize wizard which will copy the tables
> to the SQL Server and establish ODBC connections to these. Some tweaking
> will be needed but the time for this is usually counted in days rather than
> months.
>
> I've seen several apps running extremely well this way contrary to all the
> bad opinions regarding ODBC. That said, your app may of course be different
> and a rewrite may be the only way out but - as Jim has explained - the work
> load to achieve this is a magnitude larger and in some cases may not pay off
> and the time would have been spent better (and indeed at more fun) doing a
> complete rewrite with Visual Studio or the like.
>
> /gustav
>
>
>