Re: Source/object mis-match

You might ask if anyone knows about the site's programming standards & if
they have been followed religiously.  Do you have some document some place
that spells out any such rules?

I use QDOCSRC for the purpose of telling PROGRAMMERS what's going on &
something in the generic BPCSDOC for a larger audience.  The first document
in our QDOCSRC is A_READ_ME with purpose statement & navigation guidance to
all the documents.

Example: I develop something in the TEST library, we do some tests, the
results are real good but we want to tweak it a bit more before going live,
then after a while everyone is pleased.

Now we could copy the execution objects from TEST to LIVE, but I do not like
that approach because 6 months later there is a request from someone to do
another modification & thanks to PDM-54 I can see that the version in TEST
source has stuff not in the LIVE source but I cannot remember if the TEST
work was something we abandoned or if it was something implemented.

The way I prefer is to rename the LIVE source with some letter appended as a
backup just in case of the old good source, then copy the TEST source to LIVE
& recompile it in LIVE, so that the TEST version, if we hang on to it, is in
sync with the LIVE version.

If your shop has had multiple cooks, it is possible that different people
have been handling this different ways, so you not have a consistent story
with object management.

MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)