This will cause the maillist browse to display the names in alphabetical order, but is entirely irrelevant to the linking of the two tables which is why it was not shown above. Although we have not used the maillist ID's in our program, it is always a good practice to provide unique ID numbers for each record in every table so as to be prepared for setting up relations. But . . . Test the code above by entering it and adding the following code to it. 20,10 say mlCat.
Category activate window windList return .t.
Data Entering the Category Finally, we must handle entering the category when editing our mailing list. Our maillist table does not have a field with the category in it since we added only a category ID field, with the actual categories being in a separate table. The maillist table has a CatID field. The get mlCat. But we prevent direct data entry via the when clause.