Resend vs. Number 1 TipSave Often! Nothing is more frustrating than losing hours or even days worth of work. In or to avoid losing hours of valuable work time, remember to save often! It is, however, not even advisable to have days worth of work.

Author:Mazur Nimi
Country:South Sudan
Language:English (Spanish)
Published (Last):16 June 2018
PDF File Size:16.87 Mb
ePub File Size:12.25 Mb
Price:Free* [*Free Regsitration Required]

Resend vs. Number 1 TipSave Often! Nothing is more frustrating than losing hours or even days worth of work. In or to avoid losing hours of valuable work time, remember to save often!

It is, however, not even advisable to have days worth of work. As a general guideline, updates to the model must be made at least once a day.

You never know what might happen. Figure 1. These folders are the location of your generated files. In Figure 1. Cool:Gen can only read model names that have. The name of your model can be no more than eight characters in length. Figure 2 below shows the image and the message that are displayed when the images that you used during window design are not in the bitmap folder.

Remember that when you get unhappy faces, you just need to check your bitmap folder. The following files mentioned below are files found in the models. The significance of some of the files are described below.

Data Files There are four data files that make-up the entire Cool:Gen model. These files can transferred to another workstation or another. Contains key information about the model: global variables such as long model name, subset name, and software version.

Contains all the changes to the model such as add, delete, or modify object This file is the basis for the update. The size of this file may influence when an update of the encyclopedia should be performed. To improve the performance of automatic check-in and check-out, select the file transfer option found on the workstation toolset; select Options, then Encyclopedia Communications.

If your model is large or transactions have been frequent, update often. Periodically, check in your model to reduce the size of files and reduce fragmentation in storage. Failure to check in periodically can eventually result in a fatal error when you try to check in a model.

The error occurs when the IEF DAT file exceeds its maximum record count. The accompanying message is: "Memory error: No more record structures available. You can also improve performance by lessening contention. Do this by checking in changes on a regular, daily basis.

You may wish to designate times for check-ins, check-outs, and other maintenance. Refer to the concurrence matrix for encyclopedia operations that can and cannot run concurrently. Transaction Files checkout. The size of this file varies depending on how many objects were specified in your subset definition and included during expansion. Caution: The checkout. Always check the model retrieval status report. It is usually wise to create this.

To play it safe, always send an update at the end of the day or whenever you have done a substantial amount of work. This file will be sent to the encyclopedia to update the model. When uploading changes, the user has the option of updating with checkin or updating without checkin.

Regardless of which option is chosen, the update. It brings in a report of what objects have been added. Once an update has been performed, no further modification should be done until a verify has been made.

This will cause the workstation model to become out of sync with the encyclopedia on the host. These are used by the model for displaying the model retrieval status reports. These files are Important in determining what type of downgrades occurred during checkout. The format can be read only when you go into the reports menu item in the Cool:Gen toolset. DNX are your Duplicate Name report files.

These files are used by the model to display the status of a successful checkin. By selecting Model Info from the main Cool:Gen window, the developer can view important information about the subset located on the workstation. It tells you the location of your model and the local name. It indicates the status of your model whether its checked-in, checked-out, or even whether it had failed an update.

It also indicates the maximum number of objects you can create in this subset. Unless you do a HUGE amount of work, this number will not be exceeded.

Each time a subset is checked out or an update of the encyclopedia is performed, a report is created. It will show any conflicts or errors that may have occurred during the check-out or update process. The list of reports on the workstation can then be accessed by selecting File Open from the Reports window. Whenever you do a checkin, Cool:Gen creates a report for you based on the date and time the action was done.

If a checkin was executed, you will see an Encyclopedia Update Status report. On the other hand if a checkout was executed, you will see a Model Retrieval Status report. It is very important to review the reports. When you do a checkout, make sure that the timestamp of the report matches when you did the checkout. This is important for non-seamless checkout because you could be using a checkout.

The Paths pop-up window lets you define subdirectories to read from or write to when storing files regarding data, output, models, record, and work. It is launched by click on Options Paths on the main Cool:Gen window. Models: Specifies a path for the subdirectory in which Cool:Gen stores and accesses all files that define or relate to specific models.

The field design list is an excellent way to see the state of all of the export views in the procedure. The developer can define an attribute by clicking the PROPerties push button or by double clicking on the attribute. The field may have been placed on a window and later removed, but the mapping still exists. If the attribute is not coupled with one of the three characters above, then its properties have not been defined for use by the current window or dialog box.

Attributes which are defined d can be used to manipulate disable logic within a window or dialog box. Take the situation illustrated below in Figure 6. Figure 6. This eliminates the need to place fields outside the barriers of the window widen a window, place a field on the edge, and return the widow to its original size in order to provide an alternate means of disabling a field or control. When defining an item that is part of a menu structure, the developer has some additional options that are not available when defining other controls.

The special actions Cut, Copy, and Paste can be used in association with menu items only. As Figure 7 shows, Cool:Gen takes advantage of the clipboard within the operating system to perform this function.

Performing this task is as easy as clicking a checkbox. The trouble here is knowing where to find it. It contains the checkbox which needs to be turned off in order to prevent the Window and Help options from being generated. Once a list box is placed on a window, the developer can adjust the width of the columns. This is done by placing the cursor over the column divider line until a double arrow appears.

Figure 9 shows a doubleheaded arrow in between the columns status and date-entered. From there, it is a simple click and drag procedure. There are a couple of simple, yet very important, things to remember when resizing list box columns: Even though the edit pattern characters are not running into the next column, this does not mean that user entered data will automatically fit in the space provided.

Font size and the specific width of each character in the font must be considered before determining the proper column size. Resizing list box columns will affect how the data lines up with its associated column header prompt. The headers must be moved independently their position does not change when a column width is adjusted. In order to associate a export group view with the list box control, the group view must contain a selection character.

When setting up the properties of a list box, the developer can specify which field will act as the selection character by highlighting the desired field and clicking the PROPerties button as shown in Figure This action will open the List Box Field Properties Box and the developer must then check the selection indicator field at the bottom of the dialog box. After the checkbox is checked and the window is closed, the field designated as the selection character will have a d next to it.

This means that the field has been defined, but will not be placed on the window. Each list box must have a selection character if it is to work properly. The selection character is what Cool:Gen uses to determine if a row within a list box has been selected.

By cycling through the members of a group view within TRACE, the developer can see which row has been selected. By allowing extended selection, the developer gives the user the ability to select multiple rows by holding down the shift or control keys while clicking on items within the list box. Likewise, the - is used to show the last field being unselected using this method.

Mapping is the process of assigning Import Views to Export Views.


Cool Gen Tips and Tricks 1

Current Systems Analysis. Shipment Employee. Basic Customer Name. Designed Product Code.



Respected Sir! Post a Comment. There are set of questions that can help build expertise. Submit comments if you have any questions, or suggestions..


Thanks, Thanuja. I am interested in some training material on Coolgen to start learning from the anybody help me out with any kind of information or. Understand how to interpret a data model for action diagram logic, including performance and efficiency of different types of READs. The encyclopedia allows for large maherial development — controlling access so that multiple developers may not change the same object simultaneously.

Related Articles