﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Calyx Software Message Board / Calyx Point / Data Import / Export  / Import file does not update the index / Latest Posts</title><generator>InstantForum.NET v4.1.4</generator><description>Calyx Software Message Board</description><link>http://messageboard.calyxsupport.com/</link><webMaster>support@calyxsoftware.com</webMaster><lastBuildDate>Thu, 08 Jan 2009 06:03:34 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Import file does not update the index</title><link>http://messageboard.calyxsupport.com/Topic6800-6-1.aspx</link><description>If anything is incorrect in the command line invocation of import.exe, this can happen. In addition, the folders specified on any mapped network drive should follow the full UNC path format. They must match the paths in the winpoint.ini file exactly.</description><pubDate>Fri, 25 Jul 2008 10:33:28 GMT</pubDate><dc:creator>mwm50</dc:creator></item><item><title>Import file does not update the index</title><link>http://messageboard.calyxsupport.com/Topic6800-6-1.aspx</link><description>Hi&lt;P&gt;We have a process that we import application information from a website and use the import.exe function to import files into Calyx. The problem is that very frequently, but not always, after the import process is completed, the file does not show up when you perform a search for the file.&lt;/P&gt;&lt;P&gt;We have verified that the actual .brw files are in the \borrower folder  but not visible under the search outputs. It does not matter if we search by filename, borrower, etc they do not show up. The only way we can see the files is if we do a "Rebuild list" on the data folder. After this, we have no issues with the actual files missing data. &lt;/P&gt;&lt;P&gt;This happens with Windows XP Professional and Windows 2000. It started when we were using version 5.1 and has stayed around through several updates.&lt;/P&gt;&lt;P&gt;Any thoughts?  We originally thought it might be a lock problem as many of our users use shared data folders on network shares and the .idx might be locked by another user. We have discounted this as it also happens to users on their Primary Folder on the C:\ drive.</description><pubDate>Wed, 11 Jun 2008 14:05:19 GMT</pubDate><dc:creator>EHald</dc:creator></item></channel></rss>