Browsing SQL-Based Tables

Top  Previous  Next

This topic presents some techniques that should be followed when browsing SQL-based tables within your generated applications.




You should not create a Browse procedure using an SQL table without a Key defined in the Dictionary.


You not only have to have a key defined, but the sort order has to be unique.

Without a unique Key defined you can have what we refer to as  ghosting effect, whereby at runtime paging up and down the displayed list can create duplicates in the Queue. So make sure that all your browses use a Key with a unique sort sequence. All Key defintions should include a unique column.


For example, if you had a unique EmployeeID component, and another Name key based on LastName and FirstName, add the unique EmployeeID as the third component of the name key.