I have been doing document conversion for roughly 15 years and there are numerous applications you can choose from that are a complete waste of time. I have unfortunately had the opportunity to work with some very cumbersome and complicated applications over the years. One of the applications we were using had modules you would have to open separately for every step in the conversion process. After scanning you would have to open the import module then you would have to open another module for document classification then another module for indexing then another module for Quality Control and another module for releasing the final product. I was introduced to a new application called ILINX Capture that changed my entire workflow. I fell in love with it. Now, I no longer have to open a bunch of separate modules to complete the conversion process. The conversion process takes place all in the same window document classification, QC, indexing, etc. ILINX Capture is so easy to use and a complete time saver. I recommend checking it out if you find yourself wasting time going through unnecessary steps when capturing and indexing your content.
Recently I had to analyze several Stored Procedures and Views in SQL 2008 to find out why a process had stopped working. Many of you have had to do the same thing and this stuff gets complicated. So along with my several pages of notes I found this article particularly useful. This is the best representation and explanation of SQL Joins I have found and wanted to share.
I have been working with Windows Server 2008 R2 64bit and Windows 7 64bit a lot lately. In doing so, I have noticed a problem when installing a specific product that requires a COM server. When I launch the MMC to access the Component Services snap-in, I find the COM object for this software doesn’t exist. I have double-checked this until I was blue in the face. Where is that COM object? I have properly installed and can use the product, but it simply doesn’t exist in the DCOM config portion of Component Services. Like all good IT professionals, I turn to Google. (The link below further explains the problem and solution for this.) Apparently, Windows removed a process called Registry Reflection from Windows 7 and Windows Server 2008 R2 OS’s. Registry Reflection was a process that would replicate registry keys between both 32bit and 64bit registry views. Since this was removed, all registered 32bit COM objects are only available in the 32bit version of the MMC. Once you access those objects through the 32bit MMC they will replicate and become available to you in the 64bit version. To access the 32bit version of the MMC, run this command “mmc -32” from the command line.
In my experience I have noticed that many different companies do not manage their database correctly, or even at all. I have included a link to the Microsoft TechNet article describing strategies for managing your SQL database. There are lots of helpful hints pertaining to log management, backup and restore procedures, rebuilding faulty system databases, importing and exporting data, and even copying databases from machine to machine. This light reading will make you more aware of some possible issues and provide you with basic knowledge of recommended procedures to get the most out of your SQL Server.
I have included a link to the MSDN site that provides Windows Workflow Foundation Samples for many different scenarios. This is a great tool to familiarize yourself with the workflow structure we use in our ILINX Capture product.
Every since I rebuilt my laptop at work to Windows Vista I have been getting intermittent errors when opening Word 2007. I tried to live with it as long as I could BUT I I was finally fed up with it and started to do a little research on the web to see if there was a fix. As I was searching I found a forum that gave me something to try…