>Today our company was evaluating BridgeTrak Issue Management System for our support department. Our current support system is over 10 years old and getting long in the tooth. We have considered developing one in house but considered that a waste of resources. This seems to be a buy not make decision.
>
>After checking the product demo and reviewing the sales piece for the product we found that the product uses ODBC back ends such as SQL Server, Oracle, Sybase, or Access. Because of our familiarity with VFP and lack experience with SQL Server, Oracle, or Sybase, and because of the performance issues with Access we contacted Kemma Software to see if they would use VFP as an ODBC back end. This is the reply I received:
>
>"Glenn: Because of limitations of Fox Pro, BridgeTrak can not use it for
>the back end. BridgeTrak requires a SQL compliant, RDBMS, such as MS
>Access, MS SQL Server, Oracle, or Sybase. Thank you for your interest
>in BridgeTrak!
>
>--
>Jeremy Lemley
>Technical Support
>Kemma Software
>Creators of BridgeTrak Issue Management System
>Ph: (724) 452-7820 x221
>Fax: (724) 452-7836
>http://www.kemma.com
>jlemley@kemma.com"
>
>
>As I stated earlier I am not that familiar with Access, but what can it do that VFP cannot?

Glenn,

You ought to fire this question back to them (and point out the limitations that Access has when compared to VFP). There have been several threads on this pointing out its (Access) limitations in comparison and see what they say. Chances are, their reasons are bogus.