Sorry I couldn't help. Good luck.

>These are users of the software that runs their business. By definition, they have to have read-write privileges. What they can do with the data within the application is controlled by the application, not the network. They also use these MS Queries via Excel for informational purposes. Since their network account lets them have read-write access and they are accessing Excel under the same account, the solution you propose will not work.
>
>>Is the database/tables located on a network? If so, then it is your networks job to maintain the security of the database/tables. The network will only allow the users which have access to that directory. You could setup a read-only id to the directory in the network and that would control the access to the data.
>>
>>>Again, I don't have many occasions to access data this way, but she was telling me all the drivers she's worked with have always been read-only. I said the vendors must be supplying a read-only driver because ODBC was intended from the very start to allow read-write. She claimed this didn't happen with the Access driver. I was skeptical, so I fired up Excel and found an MDB file on my drive and set up an MS Query on it, selected Allow Editing, and - voila! - I edited that data with no problem. I don't know every driver she's worked with, but if they didn't allow editing I figure they must have been read-only drivers. But what's to prevent someone installing the regular driver and then editing the data? It is a security issue - the question is what's the best way to address it?
>>>
>>>>She would install VFPOLEDB. Create a UDL file and choose that as connection for query (UDL is not a must but a connectionstring representation on file).
>>>>
>>>>PS: If it's a problem, then any user with some coding knowledge and a notepad could access and update the data anyway. Excel is just making it easier.
>>>>Cetin