Good morning,

Currently the c++ code is held as you would expect in normal files Windows
files but the I am looking for a way to move them into a database. If you
have another sugeestion that fits the problem I would gladly hear it.

The problem we have is that every month these 50 quoters need updating, but
for most of the quoters most of the months, the process involves changing the
contents of the tables but not the c++ code.

At the moment programmers are used to update these tables, which is
expensive for the company and boring for the programer. There are plenty of
people within the company who have the knowledge to update the tables but who
have never seen Visual Studio and would not really be interested in learning
it, let alone learning SourceSafe to manage the projects.

So we need a very very simple source code control system, but when there is
a need for chaning the C++ code we have to use programers who obviously want
all the nice feature of Visual Studio.

We know from experience that if we have the data in SQL Server or Access
tables and a Master Folder with the C++ projects and code that the two will
get out of sync, changes will be made to the tables that require changes to
the c++ logic and this will not get done, the wrong versions of the C++ code
will be changed etc.

We tried a project where we created out own programing language which we
stored in Access tables along with the data. The Build button converted our
langauge to C++ and then the C++ compiler is called with a makefile.
Technically this works, but the langauge seems to be too complicated for non
programmers and lacking the features that programmers are used to. However
this is very easy to control, there is one Access database for all the code
and tables. Come "Next month" you just copy the Access database and press the
Build button.

We could change this to just store C++ code in the same way as we store our
own language, but our editor doesn't have intellisense, the build process is
not as slick as it is using Visual Studio and there is no integrated
debugging. So there are risks of people making changes using Visual Studio
and not copying the code back into the Access database.

I am trying to find a way of managing the code and tables in such a way that
four of five people, most of whom are not programmers can update the code or
the tables and never mess it up!

A couple of the tables in each quoter are quite large, full post code (zip
code) lists and vehicle code (about 35,000 entries) lists.

Bye

Ian