> On Friday 10 January 2003 10:17, Kevin Anderson wrote: > > Since I have no MS server, I suspect that I'll have a hard time > > implementing SourceSafe. > > heh... the turn around judo lock in chop. "welllll... since you're running > application A, we're going to force you to use application B too!"
There's two ways to see this. I see it like this. I can't use application B, but I'd like to use application A. Unfortunately, my choices have become "find a workaround" or "use application C". Unfortunately for me, Application C will take more time than I have available for this project (~2 weeks before live) right now, so it's possible in the long term, but not in the short term. The workaround is easy, have a production version, that everyone uses, and a developement version, that can be modified, and copied over the production version as neccessary. It's annoying, but it works. I actually think it's a better idea than working on a Live system, but I'm not touching any of the Database stuff. For the short term, I have TONS of disk space. (I'm at about 4% used) so they can just keep a million different versions around. Once we have a better solution (App C) or the developement is more or less complete, this shouldn't really be an issue, because things will change much less frequently. > > > CVS does the same thing as SourceSafe, but will it work correctly with > > Microsoft Products such as Access 2K. > > not as automatically, i'm sure. from their website: > are you sure you can't use a better product? or just stay with Access 97? > No problem. There is zero desire here to spend money on Windows Licenses. All this does is speed up the push to move away from MS Office. It won't happen any time soon (I'm realistic), but this is yet another reason why we're making a mistake to partner with MS. Open source doesn't limit our options in getting a job done, MS has done just that. Executives speak that language. "We bought an upgrade for Office. Unfortunately, in order to keep the functionality we had before spending that money, we also need to buy SourceSafe. In order to run SourceSafe, we need to buy a Windows Server OS. In order to use the Server OS, we'll need another server. Upgrading to Office 2000 cost $500 per desktop. In order to retain the functionality we previously had, we need to spend another $1000 for SourceSafe, Plus $5000 for Windows Server, plus $10000 for a new Server. Please note that this is more expensive than the cost of all server side software on our network in all 3 provinces combined. And where Open Source Software gave us additional functionality at a reduced cost, staying with Microsoft has required us to spend much more to continue with the same functionality we had originally started with." Kev.
