Source Code Control (WordXP)

Topic

New Reply

I would like start using Visual SourceSafe for storing my Word macros. Is it best to export all the forms and modules and check them into Visual Source Safe individually? Is the code librarian a better alternative?

Thanks

Reply | Quote

Replies

You can keep entire Word documents in Sourcesafe if you want- that would give you a complete backup, just in case of things going wrong.

If you export forms and modules, that enables you to be able to compare versions- so that if something goes wrong between one version and the next, it’s easier to track down what went wrong.

Code librarian is good for working with code you use from time to time, but (AFAIK) does not keep a history.

I like to keep two SourceSafe databases going. One is for code which is released into the wild- each time a new version goes to the customer, I keep a version in the “Customer” database.

I also like to keep a database for development work, where I’ll keep updating at regular intervals while I’m developing.

It’s easier to do in straight VB, but works OK in Word as well, just a little more awkward.

The “development” sourcesafe database is especially useful where a small team is sharing modules.

Reply | Quote

Thank you very much for your help. That helps me greatly.

Reply | Quote

Thank you very much for your help. That helps me greatly.

Reply | Quote

You can keep entire Word documents in Sourcesafe if you want- that would give you a complete backup, just in case of things going wrong.

If you export forms and modules, that enables you to be able to compare versions- so that if something goes wrong between one version and the next, it’s easier to track down what went wrong.

Code librarian is good for working with code you use from time to time, but (AFAIK) does not keep a history.

I like to keep two SourceSafe databases going. One is for code which is released into the wild- each time a new version goes to the customer, I keep a version in the “Customer” database.

I also like to keep a database for development work, where I’ll keep updating at regular intervals while I’m developing.

It’s easier to do in straight VB, but works OK in Word as well, just a little more awkward.

The “development” sourcesafe database is especially useful where a small team is sharing modules.

Reply | Quote