PreviousNext
Help > 32-bit version of the RAD Studio IDE > Easycom For Delphi connector > The Easycom IDAPI Driver (with BDE) > Connection > Testing Data Access
Testing Data Access

 Before running the Easycom For Delphi samples using BDE, you must be sure your PC is properly connected to the AS/400.

 

BDE samples are available here:
C:\Users\Public\Documents\Easycom For Delphi samples\db.

 

If you were able to run the EASYCOM installation and transfer files onto the AS/400, this can be taken as a good sign, but it's not a guarantee.

You could still experiment connection errors, depending on the setup of drivers and the AS/400 communications layer.

 

Launch Delphi. Create a New Application.

Drop a TTable component onto the main form.

Set the DatabaseName to ACE400.

Set the Table Name to SP_CUST in the EASYCOM library using the Dialog. Once you select it, a "real" connection will be established to the AS/400, which could take a while. When prompted for a Database password, press enter.

 

Note: The dialog fills the combo box list of the Table Name property. Once this is done, you still need to select one of the items.

 

Set the Active property to True.

 

Drop a TDataSource component and connect it to the TTable.

Drop a Grid component, connect it to the DataSource, you should see the AS/400 data in the grid.

 

If you have been successful with these steps, then congratulations, you have just created your first Delphi AS/400 application! You are ready to move on and do some real work with the AS/400 and Delphi. But first, we would suggest that you first take a look at the sample applications provided with Advanced Client Easycom/400 for Delphi.

 

Please notice that the Logical files associated to a physical file are visible in the IndexName and IndexFields.

 

If you did not get data displayed in a grid, then there's no point in trying the samples as they will fail.

Carefully check all of the installation steps, on the Delphi side (aliases ...), then, on the AS/400 side, check if you are receiving any error messages, and check the connectivity layers.

Use the Benchmark and Serialization programs to retest communications.