>>I didn't see views mentioned so I'm not sure if ODBC comes into play. Me no like database-level code anyway :-)
>
>Me no like it either but in some cases in might be a necessity I think. For example, I need an extensive VFP app that uses local data and the client wants to query and report against that data in Access. Granted I can setup read only access fairly easy, but I also want to protect that data from the average power user to ensure my VFP app never fails due to external playing.
>
>And the darn messagebox with fox head on field level validation is one of my pet peeves with VFP.

Use Alert :) (in the UT/Files, alert.zip). The class definition is in the code, and you may even put your picture instead of the fox (that's what I'd call user friendly, if you smile on it :).

Oh, it's for the Access folks? Put my picture to scare them off :)