Common Problems - Macro

When navigating into certain flexfields using DataLoad, the cursor may skip the first field. This can be worked around, but test any scripts thoroughly before running them with large amounts of data.

Be careful when filling in a field with text that is shorter in length than a default on the Oracle screen. For example, if the default is Expense and you overwrite with Asset, the process might input Assetse. To avoid this, append 2 spaces after the word Asset or use the *ST command before sending the text.

Navigating into a field containing a picklist in 10SC caused any entry in that field to be highlighted. This does not happen in NCA, and a new command has been added to help with this - '*ST'. *ST highlights the text in a field, so that any input overwrites existing text rather than adding to it.

The most common problems encountered are usually resolved by changing or adding delays. If spurious errors occur, or keystrokes are being missed, insert or increase a delay. To do this either use a predefined DataLoad delay or insert *SLN in the data sheet. Start with a large delay to determine if a pause helps. If it does, gradually reduce the delay to the minimum that works. Delays have helped when saving records, navigating into fields with pop lists, or when activating a menu. Delays are also key in less obvious situations, such as the following example.

Example - Timing Issues

You are running a load but occasionally data is pasted into the wrong field, in this case the field before the one that was intended. The DataLoad cells look like the following:-

TAB

Data1

TAB

Data2

The field where 'Data1' should be entered is actually being populated with 'Data2'. This can occur as follows:-

1. DataLoad sends the TAB keystroke to Oracle.
2. Oracle TABs to the next field.
3. DataLoad puts 'Data1' on the Windows Clipboard and sends 'Ctrl' + 'V' to Oracle.
4. Oracle is still processing events after tabbing into the Data1 field.
5. DataLoad sends TAB to Oracle.
6. DataLoad puts 'Data2' on the Windows Clipboard and sends 'Ctrl' + 'V' to Oracle.
7. Oracle receives the 'Ctrl' + 'V' sent in step 3 and pastes the data from the clipboard. That data is now 'Data2' and that is pasted into the field that should have received 'Data1'.
8. Oracle TABs to the next field, processing Step 5, then processes the 'Ctrl' + 'V' sent in Step 6, which causes 'Data2' to be entered into the field the user was expecting it to be pasted in.

Thus, because DataLoad is sending data faster than Oracle can process it, data is pasted into the wrong field. The solution is to slow down the speed of the load.