Installing MS Access 2007 on SBS 2003
|
Prev: Spam control in sbs 2003/exchange 2003
Next: Help Needed with SMTP Settings on Exchange and ISA 2004 SMTP Add-in
From: Steve Moss on 29 Mar 2010 19:24 I have a client with SBS 2003 R2 who has a LOB app utilising an Access database via ASP web pages hosted through IIS, and accessed from client workstations on-domain. There is no need for MS Access on the server for the LOB app to function, but the developer (who happens to be the CEO's wife) wants to install Access 2007 on the SBS to make her maintenance of the database easier and more efficient, so she doesn't have to remotely download the database, make changes, and re-upload it each time. While I can see there would be some efficiency gains for the dev that this would deliver, I am reluctant to see the SBS inevitably used for development and testing that could be done off-site, albeit somewhat slower. While I am discouraging the move, does anyone know of any technical issues that may arise from installing Access on the server?
From: April Henshaw on 29 Mar 2010 20:13 On Mar 30, 9:24 am, "Steve Moss" <> wrote: > I have a client with SBS 2003 R2 who has a LOB app utilising an Access > database via ASP web pages hosted through IIS, and accessed from client > workstations on-domain. There is no need for MS Access on the server > for the LOB app to function, but the developer (who happens to be the > CEO's wife) wants to install Access 2007 on the SBS to make her > maintenance of the database easier and more efficient, so she doesn't > have to remotely download the database, make changes, and re-upload it > each time. > > While I can see there would be some efficiency gains for the dev that > this would deliver, I am reluctant to see the SBS inevitably used for > development and testing that could be done off-site, albeit somewhat > slower. While I am discouraging the move, does anyone know of any > technical issues that may arise from installing Access on the server? For all the right reasons, just tell her it can't be done. Office is not meant to be installed on a server. Advice her of the pitfalls, the overhead to update and maintain the server with office being introduced especially the Dangers of overwriting system dlls. Next time she will ask for more, so better to just decline it now.
From: Charlie Russel - MVP on 29 Mar 2010 20:49 A FAR better solution is to set up a logon for her via RWW to a workstation internally that is running Access. This will allow her to update it from the workstation. -- Charlie. http://msmvps.com/blogs/russel "Steve Moss" wrote in message news:xn0gs8n48ei2ug000(a)news.microsoft.com... >I have a client with SBS 2003 R2 who has a LOB app utilising an Access > database via ASP web pages hosted through IIS, and accessed from client > workstations on-domain. There is no need for MS Access on the server > for the LOB app to function, but the developer (who happens to be the > CEO's wife) wants to install Access 2007 on the SBS to make her > maintenance of the database easier and more efficient, so she doesn't > have to remotely download the database, make changes, and re-upload it > each time. > > While I can see there would be some efficiency gains for the dev that > this would deliver, I am reluctant to see the SBS inevitably used for > development and testing that could be done off-site, albeit somewhat > slower. While I am discouraging the move, does anyone know of any > technical issues that may arise from installing Access on the server?
From: Russ SBITS.Biz [SBS-MVP] on 29 Mar 2010 22:02 Agree, even a Headless PC sitting in the server room would be good for this. Russ -- Russell Grover - SBITS.Biz [SBS-MVP] MCP, MCPS, MCNPS, SBSC Small Business Server/Computer Support - www.SBITS.Biz Question or Second Opinion - www.PersonalITConsultant.com BPOS - Microsoft Online Services - www.Microsoft-Online-Services.com "Charlie Russel - MVP" <Charlie(a)mvKILLALLSPAMMERSps.org> wrote in message news:ODHYLL6zKHA.5548(a)TK2MSFTNGP06.phx.gbl... > A FAR better solution is to set up a logon for her via RWW to a > workstation internally that is running Access. This will allow her to > update it from the workstation. > > -- > Charlie. > http://msmvps.com/blogs/russel > > > > > "Steve Moss" wrote in message news:xn0gs8n48ei2ug000(a)news.microsoft.com... >>I have a client with SBS 2003 R2 who has a LOB app utilising an Access >> database via ASP web pages hosted through IIS, and accessed from client >> workstations on-domain. There is no need for MS Access on the server >> for the LOB app to function, but the developer (who happens to be the >> CEO's wife) wants to install Access 2007 on the SBS to make her >> maintenance of the database easier and more efficient, so she doesn't >> have to remotely download the database, make changes, and re-upload it >> each time. >> >> While I can see there would be some efficiency gains for the dev that >> this would deliver, I am reluctant to see the SBS inevitably used for >> development and testing that could be done off-site, albeit somewhat >> slower. While I am discouraging the move, does anyone know of any >> technical issues that may arise from installing Access on the server? >
From: Duncan McC on 29 Mar 2010 22:54
As Charlie Russel says, why can't she logon via RWW to a workstation (*the* workstation w' Office (Access) and the database on it). PS: If you try just *five* users accessing an MS Access db on over a network - you can pretty much kiss your LAN goodbye - it'll slow the LAN to a crawl! If she has a few clues, she'll change the db to SQL Server (Express) - and run it "client-server" - the way it should be over a LAN. It's a trivial task. -- Duncan. In article <xn0gs8n48ei2ug000(a)news.microsoft.com>, "Steve Moss" <> says... > > I have a client with SBS 2003 R2 who has a LOB app utilising an Access > database via ASP web pages hosted through IIS, and accessed from client > workstations on-domain. There is no need for MS Access on the server > for the LOB app to function, but the developer (who happens to be the > CEO's wife) wants to install Access 2007 on the SBS to make her > maintenance of the database easier and more efficient, so she doesn't > have to remotely download the database, make changes, and re-upload it > each time. > > While I can see there would be some efficiency gains for the dev that > this would deliver, I am reluctant to see the SBS inevitably used for > development and testing that could be done off-site, albeit somewhat > slower. While I am discouraging the move, does anyone know of any > technical issues that may arise from installing Access on the server? |