To all who replied,

Thanks. Found it... my app has a security object that uses an ADO recordset that's accessed via the VfpCom.dll classes. These classes were in conflict with the Crystal Reports ADO access mechanisms. We've canned the VfpCom classes and rewritten with a more efficient methodology.

Again, thanks

Thom C.