Hi Martha,

Seems you've all the information you need. For testing, drop command button on the form and in it's click method put code that sets appropriate properties of the control and than calls CmdExecute method. Something like,

* Comanbutton Click
* Assuming that you didn't change the name of ActiveX control 
WITH Thisform.olecontrol1
  .DDFPath = <...>
  ...
  .CmdExecute()
ENDWITH

>Thank you for your response. I have a readme file and help files I've read over and over. I've pasted the portion related to executing the configuration file...(I have excuted it with the "Management facility" and achieved a successful result.)
>
>"Execution
>
>The Operation tab of the Management facility lets you execute the operations configured on the grid. It provides a window so that you can see them in progress. Only the tables whose Included column is checked is executed.
>
>4.2.3 Command Line
>
>The Enterprise version also has a command line interface. The command line can be used to execute a configuration description file (.cde, .cds). This is the same file created with the Management facilities. The command line allows you to preconfigure a set of operations and execute it in programs like reporting tools, schedulers or even via an icon on the desktop.
>
>There are two optional parameters you can specify on the command line.
>
>1) /DDF: - This will override the DDF specified by the configuration description file (.cds). This allows you to dynamically specify the path to a DDF at the time the configuration file is executed.
>
>2) /OUT: - This will override the output path specified by the configuration description file (.cds). This allows you to dynamically specify the path to output the data at the time the configuration file is executed. If you just specify the file name for the Output Location column then it will be combined with this value to determine the Output Location path and file name when the .cds file is executed. Although the Data Manager Enterprise has a command line interface we included a lightweight executable to execute the command description files from the command line.
>
>MNGREXEC.EXE /DDF:c:\mydata /OUT:c:\mydata\out max.cds
>
>The MNGREXEC.EXE file is installed into the windows\system directory.
>
>We also have included an ActiveX control for executing the command description files. You can either use it to execute the MNGREXEC.EXE asynchronously or synchronously execute the command description files from the ActiveX control. The ActiveX control is the mngrun.ocx file. The entry in the registry is MngrExecute. This is what is visible from visual basic or other tools. The mngrun.ocx file is installed into the windows\system directory. Both the mngrexec.exe and the mngrun.ocx are licensed files. Neither can be redistributed or run from a machine other than the one on which the enterprise version was installed. The are licensed with the Data Manager Enterprise. And a Data Manager Enterprise license must exist for every machine on which they are run.
>
>MNGRUN.OCX
>
>Properties
>
>The properties correspond to the command line parameters. There are also two additional properties; ExeType and ConnectionString. The ExeType specifies whether you want to use the mngrexec.exe file or the OCX to do the export. The exe will do an asynchronous export and the .ocx will do a synchronous one. The ConnectionString used to specify a connection string for database export. This connection string will take precedence over any connection information in the command description file. This only applies when the ExeType specifies OCX.
>
>DDFPath - Optional. Corresponds to the /DDF: command line parameter.
>
>OutPath - Optional. Corresponds to the /OUT: command line parameter.
>
>OtherParms - Reserved for future use
>
>ExePath - Name of command line executable for the command description files. Defaults to mngrexec.exe
>
>FilePath - Path and name of Command Description file (either .cde or .cds).
>
>ConnectionString - Optional. Database connection string. Only applies if the
>
>ExeType - .EXE or .OCX export.
>
>Methods
>
>There is only one Method.
>
>CmdExecute - Execute the command description file. Returns a long integer. How this is done is determined by the ExeType Property.
>
>a) EXE - then the ExePath is the name of the executable (.exe) file used to execute the configuration. Execution is Asynchronous. Any return greater than 31 signifies success.
>
>b) OCX - The configuration file is executed synchronously by the OCX. A return of zero indicates success. Non zero errors indicate an error occured. Note: Database errors can occur even if the value returned is zero.
>
>Even if you get successful return codes does not mean all is well. Many database errors are non fatal. How errors are handled is a grid configuration. See Record Errors and Field Errors columns. Check the export log for any error details.
>
>If the ExeType specifies EXE then the two required properties are ExePath and FilePath. If the ExeType specifies OCX then the only required property setting is FilePath.
>
>With the mngrun.ocx it will be much simpler to incorporate the execution of command description files within more programming tools. To select the mngrun.ocx from within VB either select the
>MngrExecute component name or use the browse button to select the .ocx file.
>
>Remember, no part of the Data Manager Enterprise can be redistributed. Each and every machine that it runs on must be licensed. And therefore this includes the mngrun.ocx and mngrexec.exe files. And this is strictly enforced."
>
>It seems to me there is something I'm missing between what this has produced and how I am supposed to make it work. I'm a little uncertain/unhappy if this program has been set up to require me to rack up alot of hefty support charges. I sure appreciate your interest in my problem.
>