FW Editor: What are your plans or objectives in the near future?
Jimmy Olsen: Thank you for this opportunity to share. I have great plans for the future. First, as you are reading this, idxScout Version 2.0.0 is being released. It’s a major upgrade which I’ll discuss later. I’m planning more enhancements to the system, including a ‘light’ version for non-corporate use. I have a big plan for future releases idxScout, but don’t want to share it at the moment.

FW Editor: How and when did you start writing the code for idxScout? What inspired you the most? Do you plan to develop new software, or are you more focused on optimizing the current ones?
Jimmy Olsen: The basic idea for idxScout came to me over 3 years ago. I’ve written over 1,000 queries and reports over my career. Frustration inspired me to write it. Difficulties sent me on a quest for answers. It goes like this: In my last position, data conversion, I’d encounter new databases and new formats constantly. It was such a long process to figure out how the database was constructed. Although every database tool can determine database fields and browse the data, it’s the human mind which has to decipher it. I decided it was time to make my job simple, so I wrote idxScout. I started Mid-January 2010, completed the Alpha by early March. I then devoted myself to writing a website (which I had never done before); deciding to learn HTML and ASP. idxScout went through a full test in May and was released.

FW Editor: Can you tell us more about the Key Hunter system?
Jimmy Olsen: Key hunter is the basis for database analysis. It’s a fantastic tool to find the ‘hidden’ parts of a database. It works by cross processing all tables and fields with each other. The data is compared and if it is similar it’s added to a result set. In version 2, I added primary key and index highlighting to the results set. The results can be used in so many fashions; I’m sure I haven’t discovered them all. It shows you basic keys with an instant preview. While looking the data, a developer will ask ‘why does this field have an index?’ Processing an all-fields hunt brings up the question ‘why isn’t this field indexed?’ I also noticed a design flaw in the database. The addresses were not in a separate table. It was obvious, because fields matched between tables. There’s a wealth of information contained in a hunt.

FW Editor: Is there anything you would like to change in idxScout? There are some extra features that you may like to have? Is there anything that is not working as intended and you are planning to remove it?
Jimmy Olsen: idxScout 2.0.0 has major improvements. Indexes and primary keys are colorized throughout the program. Instant preview (CTL-S) can be used ‘everywhere’ in the program. The UI is now resizable with splitters; screen layout is saved between executions. idxScout looks better, with all functions in tabs rather than pop ups, and more room for displaying data lists. It loads all its lists on startup. Oracle databases now work with idxScout (that was a challenge!). You can now ‘add’ a key using the same ‘pick it’ logic and the save logic was tightened up. I’ve removed the idxMem class support, it caused some unneeded confusion. When it’s added again, it will be isolated from the main UI.

FW Editor: idxScout has quite a strong competition but, so far, it succeeded in making a name for itself. What is the secret?
Jimmy Olsen: Create a quality product. Remember that any little frustration I have encountered through the years, others have too. Don’t accept part of an answer; let them see the whole solution. Don’t clone, invent. You’ll notice idxScout has a completely different way of looking at tables and fields than other db managers. It’s nice to have some variety, and I think this variety is much easier.

FW Editor: What are the main advantages of using idxScout?
Jimmy Olsen: I’ve gone over most of this earlier, so I won’t be too repetitious. It’s easy to use. It’s fast, showing you data with a keystroke. Gives the PC some brains so it can figure out a very difficult task; SQL Joins. But primarily, it saves precious time and money.

FW Editor: Besides idxScout, is there any other similar application that had a positive impact over you? Why?
Jimmy Olsen: I really can’t pin it down to one application. I did not want to clone existing database systems so idxScout would stand out as unique. I am impressed with Oracle’s database manager.

FW Editor: How can you characterize idxScout in just a few words?
Jimmy Olsen: idxScout. Get a bird’s eye view into your database and then start flying out SQL.

FW Editor: Can you tell us more about the most important features from idxScout?
Jimmy Olsen: I think I’ve covered everything, but for the future… boy I have some ideas!

FW Editor: Now, to end our small interview, is there any message you would like to send to idxScout users?
Jimmy Olsen: To all my customers, thank you. I’m committed to making your job easier. Remember, it’s not just your job, its 8+ hours of your life; every work day and many, many more hours of thought off the clock. We’ve all had the frustration; it drives us to do a better job. I’m happy to help make it easier for you.