Looking for recomendation for Web Based front end "AkAlan via AccessMonster.com" <u18147[ at ]uwe> 04.08.2006 18:33:06 I have just converted several mdb's to adp's and now would like to migrate to a web based product like .ASP. Does anyone have any recommendations as to which product would be the most practical. I have about 150 users on military bases and it is a real pain every time I make a change to the front end and have to push a copy out to the server and have them grab it. I will still use SQL as the backend and the server resides on a machine with a web server running. I will be more than happy to provide more info if it will help determine which software to go with. Thanks for any help. -- Message posted via http://www.accessmonster.com

Re: Looking for recomendation for Web Based front end "Norman Yuan" <NotReal[ at ]NotReal.not> 04.08.2006 20:20:50 Any server side web technology + browser as front end will do: Java, PHP, ASP, ASP.NET... It all depends what expertise you have or you ca find to do it. Neverthe less, Access ADP is definitely not a cadidate of web app's front end. Since you are asking in a MS tech. NG, on MS side, your option would be .NET. Most likely, it is ASP.NET. If your app needs quite some client side processing, you make consider Web Services+Smart client technology from MS. Be aware, going to web app, anything you have done in ADP (or mdb) would be thrown away (only SQL Server server side objects, such as tables, views and SPs could be re-used). "AkAlan via AccessMonster.com" <u18147[ at ]uwe> wrote in message news:6446ea1d2a9ce[ at ]uwe... [Quoted Text] >I have just converted several mdb's to adp's and now would like to migrate >to > a web based product like .ASP. Does anyone have any recommendations as to > which product would be the most practical. I have about 150 users on > military > bases and it is a real pain every time I make a change to the front end > and > have to push a copy out to the server and have them grab it. I will still > use > SQL as the backend and the server resides on a machine with a web server > running. I will be more than happy to provide more info if it will help > determine which software to go with. Thanks for any help. > > -- > Message posted via http://www.accessmonster.com >

Re: Looking for recomendation for Web Based front end "Vadim Rapp" <vr[ at ]myrealbox.nospam.com> 05.08.2006 13:09:09 AvA> it is a real pain every time I make a change to the front end and have AvA> to push a copy out to the server and have them grab it. I think the drop of your productivity resulting from programming web pages will far exceed that. Web programming is still much less efficient compared to desktop. Vadim Rapp

Re: Looking for recomendation for Web Based front end "Baz" <bazz[ at ]REMOVEbcap.THEeuro1net.CAPScom> 16.08.2006 08:14:59 "AkAlan via AccessMonster.com" <u18147[ at ]uwe> wrote in message news:6446ea1d2a9ce[ at ]uwe... [Quoted Text] > I have just converted several mdb's to adp's and now would like to migrate to > a web based product like .ASP. Does anyone have any recommendations as to > which product would be the most practical. I have about 150 users on military > bases and it is a real pain every time I make a change to the front end and > have to push a copy out to the server and have them grab it. I will still use > SQL as the backend and the server resides on a machine with a web server > running. I will be more than happy to provide more info if it will help > determine which software to go with. Thanks for any help. > > -- > Message posted via http://www.accessmonster.com > If your concern is purely with distributing updates, then it would be madness to redevelop your front end just to solve that trivial problem. Simply automate the process. I always set up adp systems as follows: "main" master copy of the adp file on a server "local" master copy of the adp file on each workstation "local" run copy of the adp file on each workstation (this is the one that gets opened by the user). What the users actually run when they launch the system is a vbscript which: 1. compares the last-modified timestamp on the main master and local master 2. if they are different, copies the main master to replace the local master 3. copies the local master to replace the run copy 4. launches the run copy. This ensures that (i) every user gets a nice, clean adp every time they launch the system (ii) updates to the adp get automatically distributed, all you have to do is to update the main master and (iii) the file copy over the network only occurs when it is really needed i.e. when the main master has been updated.