In order to provide flexibility to my application's users, I have created a window that allows them to generate reports in other packages by using DDE link. The user has to specify and save for later use the basic DDE link settings, the table to be used, the columns to display, selection criteria, and sorting order of the data to be sent to other applications such as Microsoft Excel or Microsoft Word.
The data transfer works perfectly well in the full developer environment, however, the DDEDATA and DDECOMMAND properties are not working in the runtime copy of my application. They generate a DDEERROR '16390' (which I believe means bad command). Even when the data volume of the full development is attached in lieu of the runtime database, the runtime version consistently generates these errors.
The DDE link I am testing is with Microsoft Word. The following is an example of the commands set to the DDECOMMAND property of the DDElink edit box.
FilePrintPreview
ClosePreview
EditBookmark .Name=DDELink", .SortBy=0, .Goto
EndOfLine
InsertPara
EditBookmark .Name=DDELink", .SortBy=0, .Add
DDESERVICE, DDETOPIC, and DDELINK work all right in both environments, and the Microsoft Word document is opened OK.
Is there anything I can do to resolve this problem? Should I mark something as publishable?