I hate com debugging, a simple task that would takes minutes to debug in Fox EXE's balloons into an 8 hour ordeal with no resolution in site. It's a pretty simple task, check to see if a particular product exists when our P.O.S. program loads, and if it doesn't, add a record to the product file (IC_PRD). Our system is ntier using Cursoradapters to manipulate the data from the backend.

** Set up product used to transfer client credits.
LOCATE FOR ic_prd.prd_prd_cd = 'CREDIT TRANSFER'
IF !FOUND()
INSERT INTO ic_prd (prd_prd_cd,prd_prd_nm) VALUES ('CREDIT TRANSFER','Transfer Credits on Acct')

IF TABLEUPDATE(0,.F.,'ic_prd',laErrors) = .F.
This.Error('SetupSpecialProducts','Insert Into ic_prd for CREDIT TRANSFER')
ENDIF
ENDIF

The tableupdate does not work and generates and error 1435 which is an XML error message when we are not even using XML. If I add a COMRETURNERROR to the error logic, Fox calls the error again.

If anyone knows how to better trap COM errors and implement some sort of rudumentary debugging technique, your comments are welcome. For the Fox team, debugging a COM object should become a priority if they want our community to deliver apps that work without spending extraornicary amounts of time.

>I hate com debugging, a simple task that would takes minutes to debug in Fox EXE's balloons into an 8 hour ordeal with no resolution in site. It's a pretty simple task, check to see if a particular product exists when our P.O.S. program loads, and if it doesn't, add a record to the product file (IC_PRD). Our system is ntier using Cursoradapters to manipulate the data from the backend.
>
>** Set up product used to transfer client credits.
>LOCATE FOR ic_prd.prd_prd_cd = 'CREDIT TRANSFER'
>IF !FOUND()
>INSERT INTO ic_prd (prd_prd_cd,prd_prd_nm) VALUES ('CREDIT TRANSFER','Transfer Credits on Acct')
>
> IF TABLEUPDATE(0,.F.,'ic_prd',laErrors) = .F.
> This.Error('SetupSpecialProducts','Insert Into ic_prd for CREDIT TRANSFER')
> ENDIF
> ENDIF