This may or may not be related to the issue in my previous post regarding compound foreign keys but I’ve found that when I import a database the primary key index is not being created. In order to create the index I have to go to the Modify Table Structure screen and uncheck and re-check the Primary Key box on the Primary Key field and save the modification.
There is a similar issue when adding the messaging and localization tables via the profile menu. The automatically generated stored procedures for the MessageItems and MessageLanguages are being created with blank names. Opening the Table Properties for each table and un-checking and re-checking the ‘Create INSERT Stored Procedure’ followed by save fixes the problem.
Lastly I added the Security Tables using the latest security package to my database. When I try to create the package I get an error message (see attachment). However if I exit DDT and rerun it I can create the package. If I try to create a package more than once I get the error and have to exit DDT.
-Larry