The advantage, is in the idea of internet applications
having to setup a -cloud- network share in addition to a sql server access- setting permissions, is just another headache for it people, where if the updates to the class and or application could be kept in the same database, and updated - synced on a login process. how should I saw this. Sweet !

you know, a built in set of functions like
Save class as sql to sqlserver

And checkappupdate(server,login,port,)

Basically, anyone I talk to, no longer thinks about network applications, without the ability to work over the internet., Which to some people mean working with terminal server enviorment, and web enviorment,- Personally, I am leaning towards client server all the way. Forget the web (html), (except for very small applications) and all my vfp data, should be stored on a sql server, so no matter where the client is, they have my application, their data, and a desktop enviroment.

At least thats the direction I am going.
Bob Lee

>>We could store our clasfiles, since they are just actually vfp tables, in or as sql server files to be checked everytime a user logs on. When an update on the class file is present, the new classfile are download to the user, or if a new app is present, it is downloaded etc.
>
>That's a clever idea, and wouldn't be hard to implement. But what advantage does this give over just copying the VCX from a designated network share? Now, I'm all for Microsoft selling more licenses for SQL Server <g>, but this seems like an expensive storage mechanism to me.