Assistance with a Crashing Key-In File

RE: Assistance with a Crashing Key-In File

caddcop — Mon, 03 Apr 2023 13:27:56 GMT

I have used Excel to create command scripts, but I found it easier to make multiline scipt files which were read and applied one line at a time. the keyin a @full_path_script_filename.scr would read and execute the lines of the file. For simplicity. we would make a temporary folder at the root of the drive with all 8.3 file names, so there was no need for double quotes.

RE: Assistance with a Crashing Key-In File

David Trejo-Rodriguez — Fri, 31 Mar 2023 20:41:02 GMT

Excel has some commands to concatenate columns.

I've personally used this to create a batch script to run a command on multiple files

column 1 column2 column 3

command filename resulting keyin

[quote userid="1406657" url="~/products/road___site_design/f/geopak-inroads-mx-openroads-forum/243016/assistance-with-a-crashing-key-in-file"] single iteration (copied below[/quote]

It might be best to post on the dedicated programming forum for help:

MicroStation Programming Forum

RE: Assistance with a Crashing Key-In File

MaryB — Fri, 17 Mar 2023 17:17:56 GMT

My first thought is...how are you using excel to generate this? MicroStation command files for batch processing need to be plain TXT files. It's possible that this has accidentally gotten saved as any other file format.

My next thought is, why are you creating one long string of keyins? Wouldn't it be easier to read/follow/debug if each command were its own line, or at least each file manipulation were its own string?

This could be something handled better through MicroStation VBA. There might be a little more overhead in learning to code it, but the code would be more robust.

It's a little hard to follow this, but I don't see anything that jumps out at me as unrunnable.