Re: Access front end for sql server



How unfamiliar could an ADP environment be?

Will form design be different? I don't think so.
Will report design be different? Not in my experience.
How about code? Well, we use ADO rather than DAO. Is this tough? Given
that ADO has an extensive and easily accessed object model with
numerous examples, while the secrets of DAO are hidden among the tombs
of MVP ancestors I can't understand how it could be. How difficult is
it to type "Find" rather than "FindFirst" anyway? C'mon now; hands up
those who knew that we can use the ` (lower case tilde) in place of
square brackets in JET sql?
Well what will be different? QUERY DESIGN! We'll be able to design our
queries and views in T-SQL; if Jet SQL and T-SQL were in the hockey
business JET MIGHT get to carry T-SQL's skates into the arena and wash
his jock-strap after the game, but T-SQL would be the big handsome guy
on the ice scoring all the goals.
But what about Access's interactive Query Wizard. Won't we miss it?
C'mon! Is this a PIG or is Oink a Conservative Election Slogan? Should
you miss it you can download the superb and free SQL Server Mangement
SQL Express utility and see how things can work in the real Database
world. Did I mention UDFs? And linked servers? Sure we can use these
with OBDC but is there any encouragement to do so?
Oh, Oh, Local tables. Gonna get me with Local Tables right? Well, of
course you can save any recordset, locally, in ADTG or XML format and
access it with a simple open command.
If I were writing this in response to most, Tom, I would say, I can do
more with an ADP than with an MDB, and I can do more with an MDB than
you can. But since I'm responding to you, I'll just say I can do a lot
with an MDB, and even more with an ADP.

On Jun 28, 11:22 am, Tom van Stiphout <no.spam.tom7...@xxxxxxx> wrote:
On Sat, 28 Jun 2008 10:52:40 -0400, Gwindor <gwin...@xxxxxxxxxxx>
wrote:

No, you can also create an ODBC connection to the SQL Server and stay
within the familiar MDB environment.
It appears MSFT is phasing out support for ADP.

-Tom.

I have been doing programming in Access for about 10 years.  I am now
being asked to make an Access front end for data that is stored in SQL
Server.

My impression is that the only way to do this is to use a .adp
application, rather than an .mdb file.  Is that correct?

Is it possible to use DAO or ADO with .adp objects?

Also, is there a good manual on making access front ends for SQL
server data?

Gwindor

.



Relevant Pages

  • Re: ADP vs. MDB?
    ... i dont believe you; sorry. ... ADP are the best platform in the world; and nobody should have to use ... MDB in the real world for *ANYTHING*. ... I'm sorry that you're a SQL wimp and you just can't learn SQL ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Future of ADPs
    ... ADP, ... Personally I don't like the database design features of ADP's. ... Regarding linked SQL tables inside an mdb, I understand there is no way ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Future of ADPs
    ... You both say that you prefer designing in SQL EM versus the ADP. ... Personally I don't like the database design features of ADP's. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Connecting to a SQL Server Database
    ... > into SQL, keep the front-end MDB and link to SQL server via the MDB. ... > use DAO as the default underlying database technology (can use ADO as well ... > then ADP is the way to go, it is a start from scratch situation (if you ...
    (microsoft.public.access.externaldata)
  • =?iso-8859-1?q?Re:_ADP_mit_"=DCbersichtmanager"_=3F_/_Export_auf_Clients?=
    ... > Nicht unbedingt, wenn du eine bestehende MDB hast, die du ... paar Testdaten auf einem SQL Server liegen. ... > In einem ADP gibt es zwar den Assistenten nicht, ...
    (microsoft.public.de.access)