<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:s="http://www.techrepublic.com/search" xmlns:dc="http://purl.org/dc/elements/1.1/"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title><![CDATA[Discussion on Using Access to build a front end for SQL Server ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596]]></link>
    <atom:link rel="hub" type="application/rss+xml" href="http://pubsubhubbub.appspot.com/" />
    <atom:link rel="self" type="application/rss+xml" href="http://www.techrepublic.com/forum/discussions/15-136596/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-05-25T09:31:13-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[access 2010 on sql 2008r2 express]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-3677807]]></link>
        <description><![CDATA[Hi,I have developed an application on access 2010, now I want to migrate the data on sql 2008r2 server Express .I used access for the front end. Can used access runtime 2010 on all my client.If not can you advise me. Thanks]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-3677807]]></guid>
        <dc:creator><![CDATA[gilbertmarius]]></dc:creator>
        <pubDate>Tue, 19 Jun 2012 11:31:18 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Nice post!]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-3584658]]></link>
        <description><![CDATA[Nice post. Here???s how you can move or convert  Microsoft Access to web in minuteshttp://www.caspio.com/extend/platform-extensions/ms-access-database-online/convert-ms-access-to-web.aspx]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-3584658]]></guid>
        <dc:creator><![CDATA[cameron.reid97]]></dc:creator>
        <pubDate>Tue, 24 Jan 2012 07:33:57 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Tengo que hacer  prueba de formularios con sql server  Maestro detalle  .]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-3453026]]></link>
        <description><![CDATA[si alguien tiene o sabe como si puede mandarme el sql script para crear las tablas y el acces con el 7los formulario maestro detalle atacan a sqlserver 2005 o 2008.Es un boom de materiales gracias]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-3453026]]></guid>
        <dc:creator><![CDATA[angelsevilla]]></dc:creator>
        <pubDate>Sat, 21 May 2011 11:59:53 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[RE: Using Access to build a front end for SQL Server]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-3407865]]></link>
        <description><![CDATA[Hola trabajo para una entidad Bancaria en la actualidad tengo con?mo front access y sql Server como motor de base de datos, el secreto esta en saber sacar el mejor provechoa cada herramienta, Access lo utilizo como capa de presentaci?n sacando el maximo de provecho ya que se integra 100% con las herramientas officce de microsoft, traigo los datos con ADO para mejorar los tiempso d respuesta e inserto los datos en tablass access para no utilizar tablas vinculadas, cuando deseo procesar mando procesar a Stored procedure de SQL server pasado los datos que requiero, la verdad los tiempos de procesos son latos y la faciidad de integraci?n es muy buena.Los tiempos de desarrollo se reducen y la facilidad de integraci?n es muy buen. Como experiencia hemos tratado de comprar aplicaciones del mercado y no nos han dado los mismos resultados, como los de integridad y mejoras en tiempo de proceso.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-3407865]]></guid>
        <dc:creator><![CDATA[Asesor75]]></dc:creator>
        <pubDate>Wed, 12 Jan 2011 07:15:44 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[HOW TO LINK MS ACCESS PROJECT DATABASE TO SQL SERVER 2000 IN A REMOTE SERVE]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-3036035]]></link>
        <description><![CDATA[Hello;Pls kindly describe how i can link my ms access project to an sql server 2000 server in the same office but different computers. I have used the client and server network utilities to setup the client system but each time i try to create a new instance on Ent manager, it returns access denied hindering the database from connecting. I actually did not use any userid and password at the server end.Could that be the cause?I tried connecting with the server TCP/Ip and name but yt no connection.ThanksMike]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-3036035]]></guid>
        <dc:creator><![CDATA[mnwuzor1@...]]></dc:creator>
        <pubDate>Mon, 16 Mar 2009 17:29:46 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Beware of 97 to 200X upgrade]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1521488]]></link>
        <description><![CDATA[VBA shifts to VB6 code and rules for nulls and object variables. It can be worth it. But it is painful. An alternative is to keep the front-end and use ODBC to attach to a backend database MSDB, SQL Server or just about any relational DB out there.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1521488]]></guid>
        <dc:creator><![CDATA[short fuse]]></dc:creator>
        <pubDate>Thu, 04 Sep 2003 08:19:22 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Thanks for the update]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1521177]]></link>
        <description><![CDATA[Yes, that helps.  I'll just install MSDE and start from there.  Thanks a lot.John]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1521177]]></guid>
        <dc:creator><![CDATA[JBo]]></dc:creator>
        <pubDate>Wed, 03 Sep 2003 17:47:00 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Switching connections]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1521052]]></link>
        <description><![CDATA[The connection information is stored in a Microsoft Data Link file with a .udl extension. You can simply edit the properties of the file to connect to a different location.I usually prefer VB as a front end until it's time to print some reports. Here, the Access report tool wins hands down. Because of it I put up with the quirks of Access programming like not being able to use the Text property unless the control has the focus, not being able to disable a control that has focus, and not being able to create control arrays.If you take the time to create class modules to do the work and use unbound controls, you can almost convince yourself you're using VB.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1521052]]></guid>
        <dc:creator><![CDATA[rick@...]]></dc:creator>
        <pubDate>Wed, 03 Sep 2003 13:23:24 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[MSDE = Free, but limited. SQL depends on use...]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1520984]]></link>
        <description><![CDATA[MSDE has a size to the database available (2 GB), and doesn't have most of the tools that SQL Server has (i.e. Query Analyzer and Enterprise Manager). The management tools are limited to command line entries. For small (under 10 users) and fairly small databases, MSDE can be a good interim choice until the need for full-blown SQL Server is needed. More info can be found at http://www.microsoft.com/sql/msde/default.asp.As far as licensing, a per-processor license runs about $4500 - $5000 (give or take who is offering the deal that week. A 5 users system runs between $1000 and $1500 retail, 10 users for about $2500. The next jump up is to a 25 user system which runs about $10,000. At that point, it becomes a matter of performance. If you have 25 light users that need constant access, then the per-processor makes sense. Keep in mind that the per-seat model is for concurent connections. 5 (or 10,25, etc.) are allowed at the dance, no more. Late comers will receive an error.G Garnergreg.garner@ricoh-usa.comMCSE, MCDBA, CCNA, CDIA+]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1520984]]></guid>
        <dc:creator><![CDATA[ggarner@...]]></dc:creator>
        <pubDate>Wed, 03 Sep 2003 11:22:54 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[What about licensing issues?]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1520971]]></link>
        <description><![CDATA[I have an Access 97 application that has been running well for years. Last night an end user received a &quot;Database has reach maximum size...&quot; error. This app is ripe for an upgrade as described in the article, but what happens when five Access 2000 users try to use my newly upgraded ADP application? Doen't SQL Server have some pretty steep licensing costs? Have you looked at an SQL Server price list? How can one decide on the version to use?]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1520971]]></guid>
        <dc:creator><![CDATA[steves815]]></dc:creator>
        <pubDate>Wed, 03 Sep 2003 10:57:30 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Which dates?]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1520834]]></link>
        <description><![CDATA[Jan 1, 1753]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1520834]]></guid>
        <dc:creator><![CDATA[dkroger@...]]></dc:creator>
        <pubDate>Wed, 03 Sep 2003 08:23:33 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[which dates?]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1520787]]></link>
        <description><![CDATA[Re this:&quot;SQL Server supports dates from Jan. 1, 1753, to Dec. 31, 9999. Access supports dates from Jan. 1, 100, to Dec. 31, 9999. You can't upsize Access tables that contain dates earlier than January 1, 1953.&quot;There looks like a mismatch in dates here.  Does SQl support dates starting in 1753, or 1953?]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1520787]]></guid>
        <dc:creator><![CDATA[Erlu]]></dc:creator>
        <pubDate>Wed, 03 Sep 2003 07:20:35 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Test v. Production...]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1520777]]></link>
        <description><![CDATA[John,If I understand your question, I think you answered it, by mentioning MSDE.  To create the Front End/Back End scenario that most Access developers are familiar and comfortable with, using an ADP, you need a copy of SQL Server or MSDE installed on your local machine.  The ADP (Front End) has a Connection property on the file menu that makes changing the target database and server very easy.  You will just need to remember to script the stored procedures views, and other object that you create in the test database, and apply them to the live database.  I'm assuming the live database is up and running, of course.  If you're developing it, and implementing it for the first time, you can back up the development database, and restore that database to the target server at deployment, and get it all at once.This Data Project option that they have given us in Access is quite powerful.  I spent a lot of time as an Access developer before they gave us this, then switched to VB.  I've gotten back into Access recently, and have really liked some of the new options, such as this one.  I guess I'm still more comfortable in VB, but this is really nice. Hope that helps,Bob]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1520777]]></guid>
        <dc:creator><![CDATA[bob@...]]></dc:creator>
        <pubDate>Wed, 03 Sep 2003 07:11:35 -0700</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Test vs. Production Environment Considerations]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1520754]]></link>
        <description><![CDATA[I have some Access 2K &amp; 2K2 apps that are set up like you mention in the article - one MDB for data and one for forms, reports, code, etc.  I link the tables and have a routine that automatically determines if I am developing it on my PC (data MDB is on my C drive) vs. running it on the client's server (data MDB is on another drive on their server.)  How do you pull this same scenario off when you create an ADP?  That is, I would obviously like to create a project that I can develop on my machine in my office without affecting the the client's copy, and then put the updates onto their server to run against the live data.Secondly, are there any differences that I would notice by developing on my machine using MSDE vs. going against the live SQL engine?Thanks.John]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/15-136596-1520754]]></guid>
        <dc:creator><![CDATA[JBo]]></dc:creator>
        <pubDate>Wed, 03 Sep 2003 06:49:22 -0700</pubDate>
    </item>
    </channel>
</rss>

