Using Profiles in DB/TextWorks

Tue, 23 Apr 2013 17:29:16 GMT

DB/TextWorks v14 added the ability to save, name, and reuse Profiles for import, export, and send mail operations. A Profile is a set of parameters used with one of these operations, typically parameters that are used on a recurring basis. For example, you may receive new records from multiple sources. Some are tagged, and others are delimited ASCII with field names specified in the top line. Set up a profile for each case, to save time and improve accuracy when importing.

Overview

Profiles are saved on the user's machine, in the textbase IDI file located in the User File directory.

Creating a Profile

Specify settings for an import, export, or send mail operation. To save the settings for reuse, navigate to the Profiles tab, type a name in the "Save Profile As" box, then click the Save Profile As button. Choose a name that will be descriptive of the settings in use, for example: Import Tagged, All Fields, No Matching.

You can save the settings BEFORE clicking OK to initiate the operation. If you decide the settings did not produce the desired result, you can repeat the operation with altered settings and resave that profile.
Alternatively, you can click OK to perform the operation, determine whether the desired result was achieved, then go back, see that the previous settings were remembered, and save the profile at that point. In the case of Import or Export, you will be asked to specify the name of the file to Import or Export first, but you can then cancel the operation after saving the profile.

Using a Profile

The next time you initiate an Import, Export, or Send Mail operation, two things will occur:

The parameters you see on the tabs will match the set of parameters used the last time this operation was performed.
The profile you see selected on the Profiles tab will match the last profile you saved or selected.

These parameters may NOT match the ones associated with the selected profile. If you select a profile, then change the parameters, then perform the operation, your "last-saved parameters" and "last-selected profile" will no longer match. This is one reason to use descriptive profile names, including as much detail as necessary.

Sharing a Profile

As stated above, profiles are saved in the textbase IDI file located on the end-user's machine. The IDI file is a text file. It is possible to copy a profile definition to another user's IDI file by copying the profile definition text. However, ensure that the profile numbers and profile count are maintained in a consistent state on the target machine. They don't have to be the same as on the source machine.

Here is an example of two export profile definitions.

[Export_Desc_1]
Format=2
ExpStoreFldName=1
ExpFldSubset=0
ExpFldShowLinked=0
AscTokToken18=|
AscTokToken19="
AscTokToken20="
AscTokToken16={CR}{LF}
AscTokToken21=!
AscTokToken17=,
ExpUpdate=1
Export_Desc_Name=ASCII: export all fields with names

[Export_Desc_2]
Format=1
ExpFldSubset=1
ExpFldShowLinked=0
ExpFldSubsetFld0=1
ExpFldSubsetFld1=2
ExpUpdate=1
Export_Desc_Name=Tagged: two fields

The summary section shows that there are two profiles, and identifies the one that was last used:

[Export_Desc_Profiles]
Export_Desc_Count=2
Export_Desc_Last_Selected=ASCII: export all fields with names

Inmagic Knowledgebase

Using Profiles in DB/TextWorks

Overview

Creating a Profile

Using a Profile

Sharing a Profile