|
Home > Archive > Microsoft SQL Server forum > July 2005 > Performance Issues - Access 2000 Frontend SQL Server 2000 Backend
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Performance Issues - Access 2000 Frontend SQL Server 2000 Backend
|
|
| Michael 2005-07-04, 7:23 am |
| Hi,
Simple question: A customer has an application using Access 2000
frontend and SQL Server 2000 backend. Data connection is over ODBC.
There are almost 250 concurrent users and is growing. Have they
squeezed everything out of Access? Should the move to a VB.Net frontend
taken place ages ago?
Cheers
Mike
| |
| John@ViridianTech.com 2005-07-04, 7:23 am |
| Hi Mike,
I just completed a similar conversion if that's what you're thinking of
doing. We converted 100 forms, 60 access reports and 15,000 lines of
code "TO" 100 forms, 60 crystal reports, and 75,000 lines of VB.net
code. It was a nightmare. We spent a good 50 percent of our time
chasing down bugs in databinding itself, work arounds for tab controls
that don't work, combo boxes that don't have incremental search like in
access, radio and checkboxes that don't bind to database column nicely
as in Access...let me see, what else sucks about .net,,,Oh, it takes
freakin' forever to load a dropdown compared to access. Crystal is a
pig (eg, 30 seconds of 100 percent cpu to gen one page of output). But
on the bright side, mgmt is buying everyone new Pcs with a gig of main
memory. I guess that's good for someone.
| |
|
|
Michael wrote:
> Hi,
>
> Simple question: A customer has an application using Access 2000
> frontend and SQL Server 2000 backend. Data connection is over ODBC.
> There are almost 250 concurrent users and is growing. Have they
> squeezed everything out of Access? Should the move to a VB.Net frontend
> taken place ages ago?
>
> Cheers
> Mike
Converting to dotnet could well be a lot of work for little benefit.
If the system is of significant size then you might well want to take a
look at techniques used in Access to ensure they're IO efficient.
There again, if the system is working fine, why fix what ain't broke.
| |
|
| You should also post this on comp.databases.ms-access.
"Michael" <michael.vandeweg@za.didata.com> wrote in message
news:1120467838.034104.295910@f14g2000cwb.googlegroups.com...
> Hi,
>
> Simple question: A customer has an application using Access 2000
> frontend and SQL Server 2000 backend. Data connection is over ODBC.
> There are almost 250 concurrent users and is growing. Have they
> squeezed everything out of Access? Should the move to a VB.Net frontend
> taken place ages ago?
>
> Cheers
> Mike
>
| |
|
| You should also post this on comp.databases.ms-access.
"Michael" <michael.vandeweg@za.didata.com> wrote in message
news:1120467838.034104.295910@f14g2000cwb.googlegroups.com...
> Hi,
>
> Simple question: A customer has an application using Access 2000
> frontend and SQL Server 2000 backend. Data connection is over ODBC.
> There are almost 250 concurrent users and is growing. Have they
> squeezed everything out of Access? Should the move to a VB.Net frontend
> taken place ages ago?
>
> Cheers
> Mike
>
|
|
|
|
|