I encountered the following situations utilizing the ITSM7.5 Data Management Utility. For those who have not yet encountered this 'wonderful' inventory item:
First, installation: initial Windows 7 installation with default locations resulted in structure being under c:\Program Files(x86) on this Win7/x64 platform. Unfortunately, said structure is read-only, and did not respond to administrative change to write-eligible. Installation into c:\Users to access user space still encountered issues with writing CVS files from Excel macros, as Windows 7 security is very finicky concerning allowing macros to execute at all, let alone write files. Environment was re-installed on an XP machine, where these characteristics are no longer a hindrance. Second, filenames: this installer named the Macro files under the various sub-versions as: (workbook)CSV without a three-letter extension. System will not recognize them as Excel files at all without renaming them to : (workbook)CSV.xls (and, yes, the *CSV capitalized is hard-coded into batch files to find them for execution). Third, location sensitivity: please remember that the installation directory is hard-coded into worksheets by the installer at install time, so moving this structure (or copying from one platform to another...) requires significant attention and name-modification. Fourth, running the data import from User 7.5 : The 'convert CSV' and 'import CSV' functions each call a popup which prompts user to search for: location of DataImport.exe, location of Excel.exe, and installation directory for the overall data management structure. Yes, these will be searched the first time, as defaults noted by the Windows client are probably incorrect. CAUTION: these two popups expect DIRECTORIES--but the actual Windows search which is invoked will not allow a person to stop on a directory, requiring a standard file. Therefore, the easiest way was to selected a file WITHIN each desired directory. Then the user simply erases the filename (ONLY!) from its data window, leaving the first-level parent directory which is what the two functions require for their respective windows! Oh yes--this Data Management tool must be executed from the User Tool. Seems like a really appropriate place for the BMC development team to implement MidTier capability, right? After all, the statement of direction is that the Windows Client is headed for oblivion. I am interested in other user experiences on this item--either directly or to the list! Don W. McClure, P.E. Applications Administrator,CITC Call Tracking Administration University of North Texas dwmac @ unt . edu _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
