Creating the Automatic Box, version 4.6.6.6.


The team has constructed the driver to serve as both the source and destination, along with the container responsible for fetching data from the list of companies through the SQL command. Their next step is to create the Automatic Box to establish the link between the source and destination. The decision to utilize the Automatic Box stems from their assurance within the container's metadata that the data being read mirrors the format of the destination table, encompassing field names, types, sizes, and primary keys.


During the configuration of the Automatic Box, they prioritize specifying the type of driver for both the source and destination. Following this, they pinpoint the source container and the destination driver, ensuring inclusion of the destination table in the driver's specification. To initiate the creation of the Automatic Box, they contemplate leveraging the productivity button within the container; however, since it marks their inaugural endeavor in generating an Automatic Box, they opt to utilize the dialog box of this component itself.


Initiating the process, they navigate to Transfer and subsequently click on Automatic Box, which opens the Automatic Box dialog box. Here, they input "Load Company" in the Automatic Box Name field and furnish a description in the Description field. As their Provider is already selected, they proceed without modification.


Transitioning to the Connection tab, they meticulously select the source driver – the one it serves – and the destination driver, which will similarly be the one it serves. Despite the source emanating from a constant SQL listing solely two companies, they had to link it with a container and a driver, opting for SQL Server to facilitate this integration. With the Source selected, they proceed to designate the Source Container, clicking on Objects, then Save, and subsequently selecting the Load Company Container from the selection dialog box.


With the container now configured as the source of the Automatic Box, they pivot to the Destination section. Here, they click on the Target folder, followed by the Objects button, then Save, subsequently selecting the destination driver before clicking Save once more. However, they recognize that specifying the destination driver alone won't suffice; they must also designate the table within that driver to which they'll save the data. To address this, they click on Properties to access the dialog box.


In the Name or Prefix field, they meticulously input the table name – "GIN Company" – in accordance with their observation of the SQL Server schema. Clicking Save, they ensure all properties of the Automatic Box are securely saved before proceeding to click New, then OK. Upon revisiting Load Company, they confirm all information pertinent to this Automatic Box is readily accessible.