Ok, I've done some more reading and it's sponsored a few observations/questions for you. I would be very interested in looking at the sample, thanks for offering. From what I'm piecing together, unless you have some consistant drive mappings for all the users, you can't use the native vfp data; which is why you are using SQL Server/ODBC. Which would also mean that you've used the upsizing wizard or something else to duplicate your data integrity rules/controls that were originally in the .dbc. (Correct me if I've screwed up somewhere ;>) From a performance/distribution standpoint, I can see why it would be a plus to use AD, but I am still having trouble with the data interface end of things. It's probably just a function of our environment and/or my own fuzzy brain. We've got Novell networks with each group of people mapped to different servers and not having universal access/mapping to any one given location. SQL server isn't an option, and although we've got access to Oracle, I don't know if it's worth it for what will only be a few hundred records per year. Did you start the app design originally with SQL server in mind? I'd like to find some way to have the web server have access to the VFP data without having the users dependent on drive maps or ODBC, like how Active Server pages work. Sigh...

Laurisa Watkins
Seattle Parks Dept.
laurisa.watkins@ci.seattle.wa.us

>Laurisa,
>
>Our app is Active Document based. It works well in both an Internet and Local setting (we detect if it is running local or remote and adjust the data access automatically). For WEB access, we are using SQL Server 7 over TCP/IP for its security. ODBC is so well integrated with VFP (using SQL Remote Views), that the users can even run in "Offline" mode if they lose the ISP Connection. (Until they tightly integrate ADO within native VFP, it is simply too cumbersome to use, ODBC is proven and works well)
>
>We have a very small HTML page that automatically installs the RT if necessary then redirects the user to the APP file. I can provide you a sample if you like.
>
>See the following KB articles for help:
>
>Q182579: Getting Starting with AD
>Q107647: Connecting to SQL Server using TCP/IP Sockets
>And Chapter 31: Interoperability and the Internet from the VFP Doc
>
>We have had great success with AD, I would recommend them. But from what I read thats not the fashionable thing to say around here ;)
>
>HTH,
>Ed