RE: branding or versioning forms and reports

Paula

The 'what' command is looking for the magic string '@(#)' so you just need to use a combination of that string and the dynamic string that your source versioning system provides. I have only used VSS, PVCS and RCS but they all have the same concept. I'm sure that SCM can do it too. So in one of your form triggers you would have

vers varchar2(2000) := '@(#) $Version';

And then SCM would substitute the version for you. The what comand would work from there. You would only run into a problem if Oracle was doing some hashing/mangling of your strings in the forms binary. =8-0 But I have done this routinely with 'C' executables i.e.

static char ident[] = "@(#) $Version";

HTH Jeff Herrick

On Wed, 20 Apr 2005 Paula_Stankus_at_doh.state.fl.us wrote:

> We are working with SCM - Oracle's versioning software. We wish to put
> in the version in each form so we can do a what on the form binary and
> see what version it is. Is this possible?
>
> We are also trying to use SCCS we can compile a form then check it in
> with SCCS but when we check it out we cannot compile again. =20
>
> We would prefer to use Oracle's SCM but the issue is with "versioning"
> or "branding" the code so we can do a what and easily see what version
> the binary is.
>
> Help?
> --
> http://www.freelists.org/webpage/oracle-l
>

--
http://www.freelists.org/webpage/oracle-l