FDOT Emergency Travel Alert: For information on the current situation, please visit the following
page - 
Engineering/CADD Systems Office
When the “Revised Plans” selection rule is selected, the correct revised files are selected. When I go to build the set, I get a warning that the DeltaNDX.htm file has been selected but not all the Delta files are selected?
A:
Upon creating the set, SetMaker does a number of validations depending on which files are selected. The version of SetMaker delivered with FDOT 2004 Maintenance Release 4 was requiring that ALL files listed in the DeltaNDX.htm (including files labeled as “Deleted”) be selected. Version 3.0.1.2600 has been corrected to not process files marked as “Deleted”
- Download SetMaker.zip and extract SetMaker.exe to the \FDOT2004\win32\SetMaker directory on your workstation.
- Automated selection of Signed Files for a Signatory not updating the “Selected Files” status bar field (the files are actually selected, the status bar item is not updating)
- Projects over ~2GB would display a Math overflow error (the integer field that keeps track of project disk size was exceeded)
- Signatory filenames that contain the ampersand character “&” are replaced in the Manifest.xml file list with the XML compatible tag & (the actual filename is not changed, only the filename as listed in the Manifest.xml)
SetMaker is blowing up, or displaying error messages about files missing that when investigated, turn out to be false. What is going on?
A:
SetMaker has to validate (cross check) several files before it builds the
selection box tree view. These files include the Index (ProjectIndex.xml), the
Sheet index Report (Sheetndx.htm), Revision Report (Deltandx.htm), PEDDS
Manifest (Manifest.xml), Signatory Files, etc. .... The parser for these file
types expects data to be formatted by the programs that created them.
Sometimes, the user may have opened and saved one of these files in an editor, such as Microsoft Word, that reformats the data, or introduces foreign data that the parser in SetMaker is not prepared to handle. This may cause SetMaker to blow up, or report errors that may not be present.
Sometimes, the user may have opened and saved one of these files in an editor, such as Microsoft Word, that reformats the data, or introduces foreign data that the parser in SetMaker is not prepared to handle. This may cause SetMaker to blow up, or report errors that may not be present.
SetMaker shows the following error message, “Error in cmdCreate_Click routine. Could not load file or assembly
‘AxInterop.SHDocVw……”, after I enter my user information and press the Create Set button. What is the problem?
A:
SetMaker is working properly and is creating the sub-set and required documentation. Due to a system problem,
SetMaker cannot display the Sub-Set Manifest Report correctly. Download and extract the files in
SetMakerV3.0.1.4.zip
to the FDOT2004\win32\SetMaker folder to correct this problem.
