Adding a form using Visual SourceSafe

Creating a brand new form / service / report that has never existed before is a special case in a Configuration Managed environment. When Uniface is using the UD6/CMtool Driver it will always assume that if a ‘file’ does not exist in the ‘shadow folder’, then it does not exist.

This also applies to a new table / sub-type / library etc, but not a new register, field etc since these exist ‘within’ an existing entity (file).

So the easiest way to create a new form, is to copy an existing form file, remove its contents apart from the header and footer, check it in to Visual SourceSafe and then check it out and use it as normal.


v:\reference\bridal\components\New.xml contains:

<?xml version="1.0"?>

<?xml-stylesheet href="components.xsl" type="text/xsl"?>

<?xml-stylesheet href="components.css" type="text/css"?>

<uniface_schema xmlns:html="" xmlns="componentsSchema.xml">


If you do not follow this procedure one of two results is most likely:

* If you attempt to create a component within the IDF without first extracting one of that name into the work area, then you will get a STORE error.

*If your ‘shadow folder’ is not read-only (as opposed to each XML file being read-only which Visual SourceSafe will take care of ), then you will be able to create the new component, but it will be placed in the ‘shadow folder’ not the working directory, and you will have to add it to version control from there.

After you have copied an existing XML file from the shadow folder to your working directory, and removed all the text between the <uniface schema ...> and </uniface_schema> tags, and renamed the file, you can then drag the file from Windows Explorer to the Visual SourceSafe explorer to add it to the project database.

Enter a descriptive comment and ensure that the ‘Check Out immediately’ box is set.

The new component will be added and then checked out to your user in your working directory.

How to use the driver with Visual SourceSafe (cont.)

Configuration information
Taking control in Visual SourceSafe
Releasing a form using Visual SourceSafe
Checking a form in using Visual SourceSafe
Adding a form using Visual SourceSafe
Finding the differences in versions using Visual SourceSafe
Problems when using Visual SourceSafe

UD6 Overview
A methodology to Uniface source code control
Using UD6/CMtool and Uniface with Visual SourceSafe.

$Revision: 1.11 $ $Date: 2011/02/28 02:56:33 $[go to top]