HINT 1: It is highly suggested you first attempt your task using the User Interface prior to attempting to create an equivalent command line. Reasons for this are to:
· Make sure what you want to do can be done at all
· Makes you aware of exactly what must be specified in the command line
· You can very quickly test the command line by doing the easiest of all approaches, specifying a 'Conversion Job' file by using the /J switch.
HINT 2: It is highly encouraged that at least during the initial creation of the command line that you use the Verbose (/V) switch to see what the status of your conversion is and get any error messages. /V shows you a message telling you how the command line went. If you are not getting any message at all while using the /V switch, then see hint 3 below, as you are probably not even executing the program. If you prefer a log file instead of a pop up message box, use /L{LogFilePath} instead of /V.
HINT 3: If see the following error:
"ConvertDoc is not recognized as an internal or external command, operable program or batch file."
Then please do one of the following:
A) (Preferred method) Specify the full path to the executable. For example:
“c:\program files\Softinterface, Inc\Convert Doc\ConvertDoc.EXE” /J"D:\My Conversion Job Files\AcctBatch.SII"
Alternatively if using a batch file you might try something like this:
set CD="c:\program files\Softinterface, Inc\Convert Doc\ConvertDoc.EXE "
%CD% /J"D:\My Conversion Job Files\AcctBatch.SII"
B) Set the path operating system variable to the location of ConvertDoc.EXE
Also, it is suggested you use fully qualified paths for any files you specify. You can however specify the current folder by using “.\” syntax.
NOTE: Copying ConvertDoc.EXE from the installation folder to some other folder is not likely to work well, so instead try one of the methods above.
More:
Using 'Convert Doc' - Command Line
Complete List of Command Line Examples
Command Line Switch Specification