Access as front end, SQL Server as backend

What are the pro's and con's of an application that uses
Access as the user interface and SQL Server as the backend
database, compared with if VB is used to develop the front
end instead?DBA,
VB is more flexible but may require more expensive resources. Using VB
is more likely, but not necessarily, to produce a more stable, scalable
application. I would recommend using a .NET language such as VB.NET
It also depends on the skilled resources you have available to draw on.
If you only have Access developers, then you are limited to those,
unless you want to pay for a VB.NET developer.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
DBA wrote:
> What are the pro's and con's of an application that uses
> Access as the user interface and SQL Server as the backend
> database, compared with if VB is used to develop the front
> end instead?|||In addition to what Mark said, you have to consider what your app is
being used for, how many concurrent users will be updating data, what
is the deployment model (intranet, internet, local), is it an OLAP or
OLTP app or a combo, do you need reports, how much budget, existing
expertise, etc. The suitability of any particular client application
is highly dependent on the answers to these questions. I'd recommend a
needs analysis where you formally go through the process of asking and
researching the answers to these questions.
--Mary
On Thu, 22 Jul 2004 21:17:13 -0700, "DBA"
<anonymous@.discussions.microsoft.com> wrote:
>What are the pro's and con's of an application that uses
>Access as the user interface and SQL Server as the backend
>database, compared with if VB is used to develop the front
>end instead?