> Right. The Active Doc running on the client machine has to have the same
> access to data as a VFP local app would.

that's true. i realize the app is downloaded to a temporary internet directory on the client machine and that the app runs on the client machine. i've given
the app, access to the data on the server, by virtue of specifying the
path to the table (which remains on the server), using the UNC convention.

i've already got apps that upload and download tables using Mabry FTPX
control and perform synchronization and extractions using RPC calls, but
this is just a small app and i don't want incorporate all that work overhead.
the other apps operate in somewhat of a "batch" transactionalized mode.
i want these user changes to be available right away. i'm using DUN
access, and only a few users using it, so it seems the right way to go.
especially since i can cut a paste a lot of existing code that was written
to run against server located tables.