This indicates a field name coming out of Q&A programming that is blank in Q&A's internal field name table. This may be coming from the programming spec, or from a derived column in a report.  This can happen if fields in Q&A that are referred to in programming are deleted. There may be other internal conditions in Q&A that can cause this.

Try resaving your programming spec and all your reports in Q&A to see if any of them give you an error. In general, make sure you have done the pre-translation steps in the Q&A Translation Guide.

Quote:

When preparing Q&A databases for translation, it may not be unusual to change Field Names.  Q&A does a good job of changing those field names in the programming statements on the same database.  But that will not be good enough for Sesame.

Q&A is not able to automatically change those field names in other databases in places like LOOKUP functions, some programming that might be done in saved Retrieve Specs, Derived Columns in reports, destinations in Posting Specs, etc.  Navigation Specs might also contain LOOKUP statements that reference fields in other databases.  I have also run into instances where Field names are referenced in macros, where the macro does direct typing of a field name in part of the process.
================
In each "application" that consists of multiple Q&A databases, consider doing this for each of the databases:

Before changing Field Names for Sesame, print a text file copy of the existing Programming , Navigation, Retrieve Specs, Posting Specs, Report Specs, Mass Update Specs, etc.  

Then keep a list (keep in a Sesame database?) of all Field Names changed, listing the original database name, original field name, and the new name.  When changes are done in each database, then open up the text files of the saved specs and do a search, looking  for the old field names so you can identify other locations that may need to be changed.  

This may be overkill, but can be a  time saver on complex Q&A applications.  Even though Sesame will not convert some Q&A tools, like macros for example, at least you will already have references to the correct current names when you start to do those manual conversion steps.