Sometimes while using an XLCue function (importing, exporintg, creating a focus point, visualizing, etc.), you may have the VBA code behind XLCue "crash" on you.  This will generally mean you see the following dialog box.

At this time, you can always click "End" to continue working.

In some cases this dialog box may mean that somewhere you've put a value that just doesn't process correctly, and XLCue didn't deal with that elegantly.  In this case, you'll need to correct your entry and repeat.  The XLCue development team welcomes feedback on what sorts of user errors are most common and need help being dealt with or diagnosed accurately.

In other cases this dialog box may mean that there is a bug in the VBA code.  In this case, it's best to document as much information as possible to help the XLCue development team pinpoint the problem.  This includes noting what you were doing when the error occurred, and saving copies of the XLCue file you were using, and any USITT ASCII file you might have been importing.

To gather more information about the error, press "Debug" here instead of "End".

You'll enter the VBA Integrated Development Environment (IDE), and be presented with something like this:

Unless you're familiar with VBA and the VBA IDE and want to do some debugging yourself, the best thing to do is to take a screenshot of this window (Alt+PrtScrn to capture just the active window) and save it to pass on to the XLCue development team.