Image Mentor News and Updates

We have just uploaded the latest version of our AX Linking Utility application. Along with this, I also uploaded a presentation video of me setting up an integration between a basic database style form and a demo ApplicationXtender system.  I recommend users watch this video to see some of the power behind our AX Linking Utility application.

Some of the updates included in AX Linking Utility version 2.7, include:

• Ability to connect to the Image Mentor Licensing Service and access concurrent licensing using this service.
• Fixed a bug that would keep computer from being able to shutdown or logoff after user uses application to view documents within ApplicationXtender.
• Fixed issue where hotkeys would sometimes not work for users.

We have just uploaded the latest version of our Migration Master product. The current version is now 2.2.  We recommend everyone upgrade to this latest version.

Some of the changes include the following:

• When accessing documents, it now checks to see if it can process the entire document at one time instead of one page at a time.  All documents stored in ApplicationXtender using one BIN file can be processed at once instead of each page individually.
• Fixed various issues caused with PDF files, either being extracted from, or converted to during the process.
• Worked on issues that could cause the application to simply stop working unexpectedly.
• Brought back the ScanFile source model.
• Support for Windows 7 (both 32 and 64 bit versions)
• Added support for concurrent licenses using the Image Mentor Licensing Service

 If you would like to include Multiple Indexes Referencing a Single Document within your Index Image Import File, you can use the following example:

The difference between using a single @ sign, or using a double @@ sign has to do with the type of file that you are importing.  The documentation stats that the use of a single @ sign represents that you are importing a non-foreign file, where as the double @@ sign represents you are importing a foreign file.

 If you are importing a Single Page TIFF image, you are safe to use the single @ sign. If you are importing any other image format, including multipage TIFF images, you will need to use the double @@ sign.  I commonly will use only the double @@ sign, that way I don’t have to worry about the image format, or if it contains more than one page.

 You cannot use different field separation formats in the same file.  If you have comma values within an index field, I would recommend using a PIPE | delimiter.  I commonly will use a pipe delimiter for everything I do. I do this because typically people do not use the Pipe character in any of their index values, so it makes a better separator then the Comma does, which is commonly used in index values.

I have been recently finishing up with an update to our License Server product, and am now using the new Microsoft .Net technology.  This seems to be doing great, and I am working on finishing up with the help documentation and installer.  This new license server will allow users to purchase concurrent licenses for the following products:

• AX Linking Utility
• AX Audit Report Generator
• Migration Master

We currently have a few select beta installs of it running with AX Linking Utility and have had no issues reported.

 If you have questions or are interested in this product, please feel free to contact us at sales(at)imagementor.net

While contacted recently about Migration Master having an issue of simply stopping from doing anything, I had to spend a few days trying to figure out what exactly was going on.  The application would get to a certain point, and pretty much just stop.  It wouldn’t be using up any more resources, and just seemed to be in a deadlock.  I modified the processing engine to work completely on a separate thread, and removed anything that I could find that may cause this.. Such as any calls to Thread.Sleep() and DoEvents().  While doing this, I got it to actually start doing the same type of random lockup on the laptop I do most of my programming on. 

It took a while of updating logging to a file, and while my original thought of the issue being with me waiting for a FileCopy or Rename process to occur, it actually seemed to boil down to how I was logging my entries to a file.  I was originally using the FileOpen() FileClose() methods (probably left over from the VB 6 port over), so I changed it to use an IO.StreamWriter call to write out the entry to the log file.  Since I have done this, the issue seems to have resolved.