Re: Is ODBC right for me?

ADP is still supported in Access 2007 which means that it will be supported
to at least end of 2016 (5 years mainstream support + 5 years extended
support).

I am sure there are lots of ADPs in the real-world but the majority of
Access databases still use MDB format.

In my experience, there is no problems using ODBC provided you follow a few
simple techniques on reducing the amount of data being pulled through the
network (this applies to all Client / Server database applications, anyway).
There are a number of articles in the Microsoft KB, e.g:

http://support.microsoft.com/kb/208858

and

http://support.microsoft.com/kb/209551

--
HTH
Van T. Dinh
MVP (Access)



"DIRN" <DIRN@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BB082997-C04F-4C65-BF6F-496C53A07E9D@xxxxxxxxxxxxxxxx
I am a forum newbie - appreciate your patience.

We are embarking on a new adventure to scale up an Access DB up to SQL
Server. We are not going to use the upsizing wizardry, but have chosen to
build native SQL tables instead.

The question is which route to go with the Front-End?
- Access 2003: SQL tables linked via ODBC
- Access Data Project(ADP)
- Access 2007: SQL tables linked (MDB or ACCDB?)

We were prepared to move ahead with creating an Access Data Project using
Access 2003, but then I read the following on microsoft.com ...

" Access creates front-end applications that leverage SQL Server as a
backend data source. Access forms and reports can be optimized as
efficiently
as Visual Basic front-end for SQL Server. Office Access 2007 offers two
ways
to connect to SQL Server data: linking to SQL Server and Access Data
Projects
(ADPs).

The preferred way to connect to SQL Server is MDB file format or ACCDB
file
format. This enables you to use the full flexibility of local tables and
local queries, while leveraging the full power of SQL Server. In addition,
MDB and ACCDB files link to multiple SQL Servers and a wide variety of
other
data sources. Office Access 2007 contains many new features available in
both
MDB and ACCDB file formats, but only a subset of those features are
available
in ADPs. "

This seems to state that best practice is to use linked tables. Is this
true
in the "real world"? Isn't using the layers of ODBC going to make for a
slower app? Is ADP a technology that may not be supported by MS in the
near
future?

Where would I find info to learn how to optimize Access/ODBC to work as
well
as a VB front-end as stated in the quote above?

Your thoughts would be appreciated!


.

Relevant Pages

  • Re: From .mdb to .adp database
    ... I decided to go on with adp project, and i have created a store ... But queries are different stories. ... In SQL Server, there are Views, Stored Procedures, UDFs. ... Also, when you decide to use MDB front-end, you can choose use MDB ...
    (microsoft.public.access.adp.sqlserver)
  • Re: From .mdb to .adp database
    ... there is no exact equivalent query object in SQL Server to MDB's query. ... Most likely, the wizard converts MDB queries to Viwes or SP, if the queries are convertiable. ... Also, when you decide to use MDB front-end, you can choose use MDB queries in the front end or use SQL Server side query objects. ... SQL Server is very powerful server software, whether you use MDB, ADP or anything else to access data from it, you MUST learn how to use it and almost for sure you need to learn another programming environment. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: From .mdb to .adp database
    ... there is no exact equivalent query object in SQL Server to MDB's query. ... Most likely, the wizard converts MDB queries to Viwes or SP, if the queries are convertiable. ... Also, when you decide to use MDB front-end, you can choose use MDB queries in the front end or use SQL Server side query objects. ... SQL Server is very powerful server software, whether you use MDB, ADP or anything else to access data from it, you MUST learn how to use it and almost for sure you need to learn another programming environment. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Upsizing design considerations
    ... reports, with a ADP, or mdb (actually, it should be mde, or a ADE when you ... you would LINK the tables to sql server, and NOT USE a adp (the reasons is ... the first two remote users ...
    (microsoft.public.access.gettingstarted)
  • Re: ORDER BY in View and ADP Form
    ... MDB is for dipshits. ... this doesn't say that ADP won't be supported. ... ADP will support changes to SQL 2005. ... ...The primary application programming interface for working with the ...
    (microsoft.public.access.adp.sqlserver)
Loading