Yuri --

My error is caused specifically because columnorder = 0. The error occurs in a routine that's exporting to Excel, and the error occurs because the following statement:

	lnColIndex=loColumn.ColumnOrder
	lcColName=ExcelCellName(lnColIndex)

yields a gibberish name for the Excel column, because lnColIndex is zero. My error routine captures these values when the actual error occurs at a later line.

Jim

>Hi James,
>
>What is the error message ?
>Why do you think that it is caused by columnorder = 0 ?
>Do you have any on error routine that can identify the line of code and the code module where the error occurs?
>
>
>>My users are sporadically getting errors that are caused by columnorder = 0 for a column. I cannot duplicate this.
>>
>>What gives? I thought columnorder values were ordinal numbers 1, 2, thru n. (Note that these errors are not occurring because of any programmatic or user change to columnorder; and when the user restarts the application and tried again, all works fine.)
>>
>>Thanks