well. that is the reason they give for not continuing to use vfp as a development tool. we too ahve a sql server back end but when we start talking "com" components....the client doesn't understand and therefore....don't want to try....but we are still pressing.

Currently we have one vb, one acces, two vfp developers and you can imagine the development meetings are like!

i stand corrected on vfp not being supported by ms. the contracting company who we work for shys away from vfp as a devlopment tool to be more exact.

sorry bout the confusion.