Access front end for sql server
in [Help]
|
Prev: jobangebote immobilien stellenangebot hamburg firmen deutschland Gestalter in fuer visuelles Marketing jobangebote stuttgart jobboerse deutschland Dachdecker Dachdeckerin stellenangebote in deutschland
Next: Please Help - Can't check for duplicates
From: Gwindor on 28 Jun 2008 10:52 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
From: Tom van Stiphout on 28 Jun 2008 11:22 On Sat, 28 Jun 2008 10:52:40 -0400, Gwindor <gwindor(a)verizon.net> 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
From: Albert D. Kallal on 28 Jun 2008 12:45 "Gwindor" <gwindor(a)verizon.net> wrote in message news:3mjc645ivovma77da5lpse3js0ke4un2hl(a)4ax.com... >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? No, hopefully, if you been using ms-access, then you been splitting your databases for years? > > Is it possible to use DAO or ADO with .adp objects? When you go ADP, you can't use DAO, it all ADO by default. And, ADP projects are ONLY for sql server. if you use linked tables, then you can use just about any database server. For this reason, for existing applications, we tend to prefer using linked tables. Those tables can be linked to your back end (mdb), or linked to sql server. When you do this linking, most, if not all of your code and application sill simply function as before. This means that you can develop the application, then split it. make sure it works, and then upgrade the back end to sql server, and then link the front end to that. Here is some links that should be of use: http://support.microsoft.com/default.aspx?scid=kb;en-us;175619&Product=acc ACC2000: "Access 2000 Upsizing Tools" White Paper Available in Download Center http://support.microsoft.com/?id=241743 ACC2002: "Access 2002 Upsizing Tools" White Paper Available in Download Center http://support.microsoft.com/?id=294407 ACC2000: Optimizing for Client/Server Performance (odbc) http://support.microsoft.com/?id=208858 ACC: "Upsizing to Microsoft SQL Server" White Paper Available in Download Center (a95, and a97) http://support.microsoft.com/?id=175619 HOW TO: Convert an Access Database to SQL Server (a97,a2000) http://support.microsoft.com/?id=237980 ACC: Choosing Database Tools White Paper Available in Download Cente The Choose.exe file contains a document called "Choosing the Right Database Tools" that discusses Microsoft's database products: Microsoft Access, Microsoft FoxPro, Microsoft SQL Server, Microsoft Visual Basic, and Open Database Connectivity (ODBC). Use this document to decide which database tool is right for you. http://support.microsoft.com/?id=128384 ACC: Tips for Optimizing Queries on Attached SQL Tables http://support.microsoft.com/?id=99321 -- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal(a)msn.com
From: Tony Toews [MVP] on 28 Jun 2008 13:04 Tom van Stiphout <no.spam.tom7744(a)cox.net> wrote: >It appears MSFT is phasing out support for ADP. MSFT certainly haven't made any enhancements to ADPs for the last few versions. Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
From: Gwindor on 28 Jun 2008 14:22
Thanks. ODBC works fine for me. At least, it works fine if I can make the connection. I have tried a few different tricks to create a connection, but the connection fails. Could this be because I am working with Access 2003 and my sql server is SQL Server Express 2005? (My client has a full SQL Server copy at his location, but here at my office on my PC I am dealing with SQL Express 2005.) Gwindor On Sat, 28 Jun 2008 08:22:35 -0700, Tom van Stiphout <no.spam.tom7744(a)cox.net> wrote: >On Sat, 28 Jun 2008 10:52:40 -0400, Gwindor <gwindor(a)verizon.net> >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 |