PrimalScript tech support just downloaded an evaluation copy of FileMaker and did some troubleshooting on this issue.
They discovered that FileMaker does not properly register a type library for all their progids. It only registers it for FMPRO70.FMPRO70
You can manually associate a type library with a progid in PrimalScript going into Tools->Options->Text Editor->Type Libraries.
Click New to create New ProgID and enter the ProgID field as FMPro.Application and the type library path should be the path to your FileMaker executable like this "C:\Program Files\FileMaker\FileMaker Pro 10 Advanced\FileMaker Pro Advanced.exe"
After saving your changes, this results in PrimalSense picking up this information as it would if the type library would be correctly installed and registered in the first place.