Well, if you are driving this dialog from the MNL file you are likely using LISP, so you have options. Traditionally, you would build a DCL file & have the dialog's code in there (no information, just the code that draws the dialog itself), which would get called on by the LISP living in your MNL file, but you could potentially have the LISP file build the dialog on the fly based on which of your options is actually available at the time the code is fired. To Fill your dialog with options, you could hard-code it in your LISP program, or you could tell the LISP to fill the dialog options from either the AutoCAD DWG, or an outside file like a TXT file or an Excel file, or a word DOC. It really depends on what you are after. Which goes back to: what does this dialog do? where is the data I'm responding to? What is my desired end result when i click OK? Am I Altering the drawing in some way? Am I delivering information from 1 document to another? Am i trying to change the drawing environment to more efficiently do a task? Am I firing up the dialog, or is AutoCAD automatically responding to some condition? are the dialog options ALWAYS going to be the same, or could my drawing (or some other influence) change what options are actually available? These will all factor in on how you build this thing, and where the ending logic should live.
