[AccessD] Access and SQL Server

Hey Stuart
Thanks
Quickly and concisely cleared up many questions I had.
How to you about updating stored procedures on the SQL Server end?.

Stuart McLachlan wrote:

>A few thoughts on your questions:
>
>There is really no such thing as an SQL Server app.  SQL Server is a RDMS, not an 
>application development environment. You still need some sort of development enviroment 
>for the front end, up to you whether you use a web server and PHP or ADO.net, VB.Net, C#,  
>Access, PowerBasic or anything else which is you feel is appropriate.
>
>An SQLServer/Access is no more complex than an  Access FE/BE app if you just use ODBC 
>links to the SQL Server tables.   That is all that you need sometimes.   I tend to use Access 
>this way for reporting applications.  
>
>I generally don't use Access as the FE for data *management"  since you should not as rule  
>use linked table and bound forms to maintain data in SQL Server,  you should be using 
>CRUD (create, read, update, delete) stored procedures for this which implies going 
>"unbound".  I  use PowerBasic/SQLTools  for these applications.
>
>A major reason for using  SQL Server is user security now that MS have depreciated it in 
>Access.
>
>I update the same way that I update an Access FE/BE application.  A user runs the FE by 
>clicking on shortcut to a batch/cmd file or small application which copies the latest version of 
>the FE to a local drive and then opens it.   Updates to the BE are made by building a small 
>Updater application which modifies the backend database using ODBC with CREATE and 
>ALTER statements.  
>
>  
>