vefatica - Substituting BDEBUGGER for step 3 above fixed the problem! It appears that the debugger launch from the menu and command line behave differently. Thanks for your help. Jim

I did this: 1. Launch Take Command from the shortcut on the desktop. 2. CD C:\Projects\depot\tps\task\eagan3\src\sql\sqlserver 3.From main menu, select Tools/Edit/Debug 4. From the pop-up window, select File/Open and select the CMD file I am testing. 5. Click the start button. 6. Click the Run...

The screen captures came after it failed, so the debugger tab shows up too. I did not start that until after I changed directories. Jim

It did not work. See the screen shots in the attached PDF file. Aslo, I do not see any TCSTART file. Thanks, Jim

Thanks Charles! I will see if I can do that. Jim

I purchased Take Command last week. I have a number of CMD files to create and maintain in a number of different directories. Each has references to other files, mostly SQL scripts, and uses relative paths from the current (location of the CMD file) directory. When I load the CMD file in the...

1, 2 & 3. Prompt worked, but had some file access problems. Was unable to create a report file to track the processing. 4. Prompt worked, but was unable to open any of the files required for processing.

Edit/Debug button.

I uninstalled the 64-bit version and downloaded and installed the 32-bit version. The prompt failure with the test script is unchanged. Jim

Charles - No worries. I have found that some off-the-wall suggestion that makes me challenge some "obviously true" assumption is often the key to solving a problem. Consequently, I appreciate all suggestions. Jim

mikea - Thanks for the tip! I changed my test script to this: ::------------------------------------ :: Test DB prompt ::------------------------------------ @ECHO OFF SET LOGFILE=Upgrade_output.log SET ERRORFILE=Upgrade_error.log :: Parameters SET database=%1 SET server=%2 SET ptdatabase=%3...

Dennis - Please see my response at 13:06. It appears that the problem may be specific to the 64-bit version of tcmd.exe. Jim

I know what you mean. I have been a programmer since 1973, and I am picky about style too. CMD files are new to me, so I am too ignorant to have much of an opinion here. Jim

Sorry - that was not very clear. I changed the color to emphasize the text. The red overwrote what was originally at that position in the prompt when I entered the DB name. Jim

Charles - No changes to colors or dimensions. The window is the default that appears when running tcmd.exe. I suppose this could be a 64-bit issue. I am running 64-bit Windows 7 Enterprise edition. Would it be better to run the 32-bit version of tcmd.exe? Jim