>>We store successive versions of GENDBC's output. It is a program in your HOME() + "/tools/gendbc" directory.
>>
>>Marty
>
>Yeah, but we need data in the tables to test the app as we are developing it.

Probably the "right" solution would be to keep only the GENDBC (or GENDBCX if your database is large...) generation files in VSS, and then also have a script somewhere (probably in VSS as well) that populates the data with test data (that way you all start with the same test data). Then when it comes time to get the latest and greatest database files, you check out the GENDBC prg, run it, and run your data-populating program. There you have it.

Not, in a more practical environment, this can be a pain, especially writing the data-populating routines. We have code tables and such that we want to keep in VSS because the data is just as important and changeable as the structure is. Ah well. So, we check in the files AND the GENDBC files, and call it good. Come up with whatever scheme sounds good to you, educate the developers, and stick to it...you'll do fine.

Thanks,
Joe Kaufman
jkaufman@encompas.com