Hi Jeffrey, I've have done the same thing you are doing on serveral systems. It was sure nice working with the backend and running test on data integrity. Also, I could test the file updating part. One thing to be aware of is using VFP functions in the remote view e.g. dtos, dtoc.

Build a dbc with tables, place it on the network, build a dbc with remote views via odbc and distribute it with the application

I think it's a good idea for several reasons.

1) It's portable to any network regardless of having client server.

2) Parameterized views let you get the data you want fast enough.

3) Updating is a breeze with remote views.

4) For integrity testing it's alot easier to test on VFP tables because of free access through the back end.

The disadvantages could be.

1) Upgrading Stored procedures.

2) You may find some kinks in VFP using native tables (for one thing is out joins) The view designer generate the wrong syntax for the native tables.)