 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / General 2 / February 2007TS
I have developed a new project utilizing Access 2007 and for a client that wanted it based in one office and now wants 3 remote offices to have access. After doing my research it looks as the only decent solution is windows terminal server (I assume a new server and windows terminal server software will need to be purchased, outside IT co. to do that work). The only thing that scares me is I read that Access 2007 is not ready to run on WTS (something to do with licenses). Can someone please elaborate and keep in mind company needs to purchase Access 2007 already. My second question is they already have SQL server installed for an accounting program, how hard is it to change the backend to SQL. Thanks >I have developed a new project utilizing Access 2007 and for a client that >wanted it based in one office and now wants 3 remote offices to have access. [quoted text clipped - 4 lines] >(something to do with licenses). Can someone please elaborate and keep in >mind company needs to purchase Access 2007 already. To install Office 2007 on Terminal Server requires a volume licensing agreement of some sort. You may want to consider a runtime version as it won't have the same licensing costs as the A2007 runtime will be free. However we don't know of the A2007 runtime will work on Terminal Server. It should but until we get official word we won't know. >My second question is they already have SQL server installed for an >accounting program, how hard is it to change the backend to SQL. It can be a bit of work. A week to a few months for a gargantuan app depending on how much optimizing is required. See my Random Thoughts on SQL Server Upsizing from Microsoft Access Tips page at http://www.granite.ab.ca/access/sqlserverupsizing.htm There is a new tool from the SQL Server group. SQL Server Migration Assistant for Access (SSMA Access) http://www.microsoft.com/sql/solutions/migration/default.mspx Tony  SignatureTony 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, Thanks, so we can purchase a 10 user volume liscense and install it on a terminal server and have 10 remote offices (users) log into Access 2007 with no problems. What is the learning curve to change the backend to SQL if you have not played with it before. > >I have developed a new project utilizing Access 2007 and for a client that > >wanted it based in one office and now wants 3 remote offices to have access. [quoted text clipped - 27 lines] > > Tony >Thanks, so we can purchase a 10 user volume liscense and install it on a >terminal server and have 10 remote offices (users) log into Access 2007 with >no problems. Yes, but consider the runtime as that should work and will be free. >What is the learning curve to change the backend to SQL if you have not >played with it before. Significant. As in at least a week or so I would think. More likely two. But that's part of the upsizing curve. Tony SignatureTony 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 > >Thanks, so we can purchase a 10 user volume liscense and install it on a > >terminal server and have 10 remote offices (users) log into Access 2007 with > >no problems. > > Yes, but consider the runtime as that should work and will be free. not to sound stupid but what do you mean by runtime? > >What is the learning curve to change the backend to SQL if you have not > >played with it before. > > Significant. As in at least a week or so I would think. More likely > two. But that's part of the upsizing curve. what signs will the current backend show that signal time for a change to SQL? > Tony >> >Thanks, so we can purchase a 10 user volume liscense and install it on a >> >terminal server and have 10 remote offices (users) log into Access 2007 with >> >no problems. >> >> Yes, but consider the runtime as that should work and will be free. >not to sound stupid but what do you mean by runtime? There is *no* such thing as a stupid question. The runtime is some additional software that allows you to distribute unlimited copies of your Access app along with a limited version of Access royalty free. Prior to A2007, you could purchase this for several hundred US dollars. The A2007 version will e free. >> >What is the learning curve to change the backend to SQL if you have not >> >played with it before. >> >> Significant. As in at least a week or so I would think. More likely >> two. But that's part of the upsizing curve. >what signs will the current backend show that signal time for a change to SQL? More than 25 or 50 users. Or mission critical. Or in an environment where you don't have access to the paper should you lose a days worth of work. For example a call center. Can you imagine losing a days worth of hotel reservations or catalog sales? <shudder> Tony SignatureTony 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 |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.