>>Even assuming that it (MSDE in Access 2000 or Office 2000's Access, however you want to slice it) does allow for stored procedures, etc. it still does not appear to have logging or security beyond what Access would offer.

No need to assume here. MSDE does in fact support Stored Procs. In terms of logging, this is a feature of the SQL-Server engine. And, based on what I have read so far, MSDE is compatible with the SQL-Server engine. The VB sample on MS shows how to create an MSDE database. One example of this uses SQL-DMO. This sample not only creates a database, it also creates a log file. In terms of compatibility, the ability to support rolling back Tx's is fairly important. The log file is critical for that operation. I have yet to find anything on the site that explicitly says that logging is not supported.

In terms of security, SQL-DMO allows you to create db users. There appears to be a mixed message here. So far, it appears that you can create DB users and assign permissions in an MSDE database. Then again, while you may be able to create them, they may not be actually be implemented. This is what I need to determine.


>>to see anyone consider throwing VFP overboard

I am not advocating that. Where exactly did I say this? MSDE is yet another tool we have at our disposal. And, if you are in a SQL-Server environment, MSDE is a compelling alternative to both DBF and Jet.

Finally, it is a bigger issue than just the SQL language. The fact is, DBF's are not a client-server platform. And, when you need to develop for a C/S environment, you should use a C/S data engine.