Ok Thanks.
How then do I know the original column sequence? I thought Verify Database
would correct this.
>Crystal uses the column number and stores that. If the column number changes, then Crystal throws the error you're getting.
>
>>Do you mean the same column positions in the table?
>>
>>The SQL proc has been undergoing changes, so it's possible that the
>>positions of the columns has changed.
>>
>>Not sure why this could be an issue though? Could you explain?
Everything makes sense in someone's mind
public class SystemCrasher :ICrashable
In addition, an integer field is not for irrational people
