Reconcile Application Options

See the Knowledgebase article: Converting your application design (DSR) into a run-able Sesame application (DB) for more information on

The options when Reconciling are described in the dialog box alongside each option. Read the descriptions carefully, but most of the time the defaults will be what you want.
The five options are described below: Delete a field if there are no layout elements now bound to it?
The default is No - do not delete it. You can have a database with multiple forms. Each form has elements bound to data fields. Assume that your second form has a layout element on it that is bound to a data field called Location2. No other form or report has an element bound to Location2. If you have redesigned this form and removed the element bound to the Location2 data then reconcile it to your live application with the answer to ...delete field...set to Yes, all Location2 data will disappear from the application DB file. It is no longer needed and cannot be displayed without an associated layout element. If you answer No, the data is retained and you can rebind it to a new layout element in a later design. Answer Yes - delete the fieldonly if you are certain that you want to permanently get rid of the field as well as any data in it. This is not the recommended choice. Note that if you answer "Yes" to this question, then there will be a difference between the structure of the DSR and that of the DB file. The Designer file will still have the field (and its data), the DB file will not. Replace @Number?
The default is No - do not replace it. In Sesame there is only one @Number for the entire application. This appears restrictive, but in fact, @Number is only supported for backward compatibility with Q&A. With Sesame you can have as many @Numbers as you like by using Global Values. (See the Sesame Programming Guide for more information on @Number). Replace Global Values? The current status of all the Global Values can be seen by selecting Global Values List Manager from the Application Menu. Replace Saved Spec?
The default is No - do not include saved specs in the Reconcile process. If you choose Yes, then the saved specs in the DB file will be the same as the saved specs in the DSR file. So not only will specs be overwritten, but any added to the DB since the DSR was created will disappear. Although specs are created in Sesame runtime, not in Designer per se, you can create saved specs in Designer's Preview mode. This can be very handy when preparing Reports. Replace Security?
If you have used the Server Administration to change passwords in the runtime application with the User Management tab and wish to maintain these settings, select the default "No" setting in the area that asks if Sesame "Should reconcile replace the Security in the target application". If you are making security changes in the Designer file, and you wish these to be reflected in the runtime application, select "Yes".