Solution
Please follow these instructions to delete items from the database:

• Stop VisualStore
• Open a DB2 Command Line Processor CLP
• Press Quit
• Run db2 connect to VSTORE to connect to the DataBase
• Run db2 delete from xref
• Run db2 delete from item

Restart Visualtore, start task 3.1 Item Maintenance or task 7.8.5 Database Command Center to verify that all the Items has been cleaned up from the DB.

Solution
All text fonts are True Type fonts. Fonts are saved on disk in files with a maximum eight-character file name and the extension .TTF. Each file contains one font of a specific type and size.
There is a set of fonts supplied with the system that is proposed by the touch screen maintenance when the user selects a font for an object. All available font files are stored in the directory C:S3_EXECTSFILES on the server and are transferred to the POS when they are needed.
It is possible for the user to add additional font files by storing them under C:S3_EXECTSFILES. After saving the font files, open the VstoreServer.ini (under s3_execvsguiServerResourcesSettings) file, and look for the [TouchScreenMaint] section.
The Font section starts with the following line, indicating the number of fonts stored under C:S3_EXECTSFILES:
FontsNumber = 3
Remember to update the value for this parameter if you add new fonts in the TSFILES folder.
For each new font file added, the following 4 parameters must be specified:
FontName = Free Sans
FontDescription = Free Sans
FontFileName = sans.ttf
FontSizen = 8, 9, 10, 11, 12, 14, 16, 18, 20, 22, 24, 26, 28, 36, 48, 72
FontName: font name, this description will be displayed in the Touch Screen maintenance.
FontDescription: font description.
FontFileName: font file.
FontSize: list of enabled font sizes

Solution
VisualStore allows operator to sign on using barcodes.
Here follows a list of the settings to be defined in order to use this feature:
• Create operator barcodes: barcodes can be created by means of the Employee Maintenance (menu 8.7). Create employees by identifying them with barcodes that can be up to 22 digits long. The barcode prefix is defined in the Store Parameters Maintenance (menu 3.4.3), by the EMPLOYEE_NUMB_PREFIX (Prefix for Employee Number) parameter. Remember to associate the employee number to an operator by using the OPERATOR ID combo box. Once an employee is associated to an operator, you will see the employee barcode in the Operator Maintenance as well, in the EMPLOYEE CODE field. The Employee Maintenance also gives the possibility to use the ASK FOR PASSWORD flag. If this option is flagged, the sales application will ask for the operator password when an employee code is used for sign on. Employee codes are also used for employee identification for promotions.
• Enable the ALLOW_SIGN_ON_USING_CARD (Use employee codes to sign on operators) parameter in the Store Parameter Maintenance. This parameter enables the sales application to recognise employees barcodes.
• If you are using MSRs, remember to properly set the parameters concerning MSR in the Employee section of the Store Parameters Maintenance.
• The last useful parameter is ALLOW_MANUAL_INPUT_OF_CODES (manual input of customer/employee codes): if this parameter is enabled, you are allowed to enter employee codes manually, in case the barcode is not recognised by the scanner/MSR.

Solution
Gift baskets characteristics
A Gift basket is a collection of items that are put in a basket and sold as a single item at special times of the year (e.g. Christmas).
The total package may be sold either for a higher or a lower price than the sum of the units (preparation time, wrapping, etc.).
Only normal items are allowed in a gift basket: no weight items, price required items or department/price items can be part of the basket.
The gift basket information is sent to the POS so that it is also possible to sell the baskets when the register is off-line.
It is not possible to void or refund individual items from the basket. The whole basket must be voided or refunded.
Individual item details are printed on the receipt (where you do not have a single entry for the basket item, the basket is exploded) and the invoice.
VAT is consolidated correctly according to the departments the items belong to.
Use menu 3.9 to define baskets (first, select the store you want to assign the gift basket to).
When the ADD button is pressed, the basket barcode is automatically assigned by VisualStore. By default, the basket prefix is 0202, but it can be modified in the Store Parameter Maintenance (3.4.3), BASKET_CODE_PREFIX parameter (in the Basket area).If this parameter is modified, remember to update the BARTAB too!
Enter the basket price, and the basket expiry date. If the basket price is higher than the sum of the items composing it, VisualStore will use a dummy item to justify the price difference. The dummy item details are printed on the receipt and on the invoice. The dummy item must exist in the database, and its barcode must be indicated in the Store Parameter Maintenance, BASKET_TECHNICAL_ITEM parameter.
If the basket price is lower than the sum of the items composing it, VisualStore will use a technical promotion to justify the price difference. The technical promotion is hidden in the promo maintenance, but its ID is indicated in the Store Parameter Maintenance, BASKET_TECHNICAL_PROMOTION parameter. The promotion details are not printed on the receipt.
By default, when you create an item, its status will be “not sold”, thus meaning that the basket code will not be recognised at the POS. After saving your basket, remember to change the status to “sold”. This option can also be used to create a gift basket black list, if needed.
Add the items to your basket, you can use the F12 utility to search them in the item maintenance, press ADD ITEM and specify the quantity for every item you are inserting in the basket.
Sell the item at the POS by using its barcode.

Cause
When the server application is loaded, a flag file called MENURUN is created to prevent the application from being started twice on the same machine. The file is deleted when the application is shut down correctly. If the application is not cleanly shut down, the file may still exist. If this is the case, it will prevent the application from subsequently being loaded.

Solution
To fix this problem, erase the file s3_execmenurun and restart the application.

Solution
This error message is displayed on the sign-on screen the first time the server application is started when VisualStore is installed using sample data but data is not completely loaded.
To get around the problem the sample data needs to be loaded manually:
a) Run the s3_execloaddata.py program
If the problem is not fixed, delete the stcvr flag file, run setsample.bat (setsample.sh if the OS is Linux®) with the number of stores as a parameter (ex. setsample.bat 2 if you want to load data for 2 sample stores)
and then run s3_execvst5xmlf. Check the task manager to make sure that the task job is completed (the vst5xmlf task creates the host0timestamp.old file before stopping).
b) If calendar data does not exist (you cannot open the store), run
s3_execvsu5cale.

Solution
You need to use the following parameters for the report in menu structure maintenance, in order to obtain a report in html or pdf format by default.
Select the report from the menu:
/silent action=save save_file=filename.ext
In this case, ext can be pdf or htm(l). By default the file will be stored in s3_execvsgui, but you can specify a different path as part of the file name.

Solution
During installation, the POS uses PXE to boot and install the register. After installation, it is not necessary to use PXE, so you can change the BIOS settings so that the register no longer boots using PXE.

Solution
The program that performs the import of database data into the VFM files is called vsu5load. You can type vsu5load /? to see all the options.
For a full load, you can use:
vsu5load /V /D /I /A /B /C /E /F /G /M /N /O /Y /W /S
/Basket /Empcode /Reason /Voucher /Inifile
Alternatively, you can just execute the loaddata.py script that reallocates the VFM files followed by a full VFM load.
See VisualStore Implementation White Paper for further information.