Having created a shortcut or browser link to the Forms executable that contains the "record=" parameter, as described in Setup, you are ready to create your load.
As soon as you start an Oracle Forms session using the record parameter all your actions are recorded to a log file. DataLoad will later be editing this file and it is important that you follow certain rules to help DataLoad correctly interpret what it is you want to do. DataLoad interprets the file in two sections. The first is the header which is run once for your load. Typically this will log you in to Oracle Applications, open the form you will be working in and put the cursor in the first field used for your load. The next section is the repeating section. When you open the file in DataLoad each record you entered will be loaded in a DataLoad row. Similarly, each additional row you add in DataLoad will later result in a record being loaded into Oracle.
DataLoad interprets a row as all your actions from the first time a value is entered into a field until the next time you navigate into that same field. Since you may have to do certain actions in the form before you enter data into a field it is important that these same actions are repeated before you click back into that field at the end of your first "record". For instance, if you are querying back records and changing values, when you enter your first value the form will be in Query Enter mode. After the data has been queried back and changed it is vital that the form is again in Query Enter mode before you navigate back to the original field.
Although DataLoad will work if you do just one cycle of work, it helps DataLoad to calculate what actions are required if the process can be repeated twice. That is, you enter two records, or query back and update two records, for example. When you have done this it is vital that you exit the Applications because when DataLoad processes the file it uses this to determine when you have finished your work. To exit the Applications select 'Exit' from the Action (10.7 or 11.0) or File (11i) menu. Alternatively, in 11i you can exit the Applications by clicking the 'X' icon at the top right of the parent window, not the form. Although there are other ways to exit the Applications these are not supported by DataLoad.
In general, where multiple records are entered each record must use the same navigation and commands to the same fields and in the same order. However, the at the end of the final record you may want to alter the commands entered. For instance, instead of saving your work at the end of every record you may wish to do so only at the end of the load. DataLoad fully supports this and where a different sequence of commands was entered after the last field on the final record these commands will be used at the end of every load in place of the navigation and commands otherwise used at the end of every record.
Once you have exited the Applications you should retrieve the file created and open it using DataLoad. If you are running Smart Client then the file will almost certainly already be on your PC, however in NCA the file will have been produced on the middle tier and must be copied from a server to your PC. If your server has access to the same network drives as you do then the HTM file could be setup so that the forms software writes the file to a shared directory. If this is not possible and the file is written to the middle tier server then you must copy the file from that server. If the server is running Windows NT then you may be able to map a drive from your PC, otherwise you will have to use file transfer software such as FTP. Your DBA or system administrator may be required to help you do this.