I see, it's a tough one. Do you have any CANCEL command in your code?

I only know that I was getting this error if trigger failed and it had its own on error or table rule failed. Seems like this is not your case and unfortunately I don't have other ideas :(

>Thank you Naomi,
>
>I do not find this error 1099 documented anywhere. I do not get any additional parameters in ayError[,] Using free tables.
>
>prior to the error I generate:
>
>2007-04-25T14:22:28 = CrystalRuntime.Application.11 object created
>2007-04-25T14:22:29 = Crystal Report Opened for =util_markup.rpt
>2007-04-25T14:22:29 = SQL login OK
>2007-04-25T14:22:29 = Default parameters OK
>2007-04-25T14:22:29 = Specified parameters OK
>
>all OK to this point
>the error generates this:
>
>2007-04-25T14:22:29 = RunReport CATCH trap util_markup.rpt
>2007-04-25T14:22:29 = FoxPro Error Occurred
>Error Number = 1099
>Error Message = Procedure canceled.
>Error Parameter = No Parameter Available
>Work Area =Not Work area Related
>Trigger =n/a
>
>from this in an error trap:
>
>OTHERWISE
> * FoxPro error (took out stuff to send this to UT without complaints)
> (you cannot include a style attribute inside a tag??)
>
>This.cErrorType = "FoxPro Error Occurred ="
>Error Number = ALLTRIM(STR(ayError[1,1])) ; && VFP error number
>Error Message = ayError[1,2] ; && VFP error message.
>Error Parameter = IIF(ISNULL(ayError[1,3]), ;
>No Parameter Available, ayError[1,3]) ; && error param
>Work Area = IIF(ISNULL(ayError[1,4]), ;
>Not Work area Related', ayError[1,4]) ; && application's Help file
>Trigger = IIF(!ISNULL(ayError[1,5]), ;
> IIF(ayError[1,5]=1, Insert trigger failed'
> IIF(ayError[1,5]=2, Update trigger failed'
> IIF(ayError[1,5]=3, Delete trigger failed'
> 'unknown'))), 'n/a') && failed trigger
>
>
>>This error sometimes comes from failing trigger / table rule. Could it be the problem in your case?
>>
>>>aerror() gives me:
>>>
>>>Error Number =>1099
>>>Error Message =>Procedure canceled.
>>>
>>>What error is this?
>>>
>>>calling a CrystalRuntime.Application. setting parameters to run reports. I run about 150 different ones in a batch with no problerms, but I get this error on about 14 of them. I have looked over the reports and don't see anything wrong.
>>>
>>>Thanks for suggestions/directions
>>>
>>>Al Allison