>>Can you tell me some, I wondering what complications you did find that I didn't find. Especially for lookuptables you don't have to worry about RI that much.
>>
>
>Try having to replicate out to many sites. It either all has to work, or none of it should work, in order to keep all sites consistient. It is a PITA to manage. Once again, Walter, you are more of a theorhetical guy. Getting out there and really doing it on the other hand, is another thing all together..

Well I assume you're talking about a single SQL-server that is accessed trough a WAN, don't you? If the SQL-server was local (LAN), You'll not have any problems replicating the data into a VFP database. If working with multiple servers I think you could first replicate it to the other server which in it's turn replicates it into the local VFP database.

In your case of one SQL - server accessed by many different client from different sites trough a WAN i've got to agree. Replication isn't going to be handy up here.

I would really appriciate NOT to belittle me on the experience side. I have experience with working with SQL -server 6.5. The way you try to belittle me I can also apply on you personally because of the lack of theoretical knowledge of the basic priciples of relational databases. So please, don't....

Yes, I'm a thinker, but when I develop a theory, it will be examined into practise. No-one will ever catch me on saying things that are impossible in practise.

>>How does active directory fit in here ?
>
>It would take me too long to explain here to do the topic justice. Best for you to go to msdn.microsoft.com, and search on the exact phrase "Active Directory".

I will...

>The corporate standard is SQL-Server. i.e., storage mediums like DBF's are deemed to not be secure enough. Now, what are you going to do? And, if you think this scenario is odd, it happens all of the time...

Well, the storage medium IS SQL-server, you only want to have local lookup tables for performance advantage, which is replicated from the SQL-server. You can also include a stored procedure which forces the renewal of the lookuptables to ensure that they're in sync. Of course you can do this periodicly also.

In your case STP make sense, in my case replication makes sense.

Walter,