>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?

I don't think that's the issue - I think they're using it as an excuse for business/marketing reasons.

It's possible they don't know VFP data can be accessed via ODBC. My suspicion is that no-one has asked them for it, so they haven't yet developed a VFP database to support their app, tested it, got it to work acceptably with VFP ODBC, etc. - a process that can cost a lot of money. They aren't likely to undertake this for a single sale unless they can turn a profit on it.