Yes - that’s one reason I havent set one up before (along with the fact that there have been a total of about 2 people making source changes), we have many different source types - and often very thought has been given to writing re-usable code due to the extreme custom solutions we provide - we never do the same thing twice.

So,
- we have very few re-usable code blocks.  Of those we may have, source may be vbScript, javaScript, VB, vb.Net, c#.

- we currently store each source file under the specific project.  This provides for the flexibility we need but almost no re-usability (I think I have done that before, search through all the previous project folders and if I find something I can use, copy it and start modifying).

- we very seldom have a development project (like a vb or c# solution) big enough that multiple people are working on it at the same time.  But it is becoming possible to have >1 people editing the same eForm source (html file).

- it is up to each individual to be sure their latest source is in the correct project location for backups and for hand off to another person.  This becomes complicated further by the fact that most source is text-editable and often times quick fixes / changes are made on-site during install/config/testing.  Sometimes those changes may not make it back to Keymark.

This is probably more than you were asking for - but it the explanation of why this is more than a simple revision control on development source files.

We can talk about this as well if you like.
kb