Russel,
I don't know of any readonly driver (and having one is nonsense). As you said it's a security issue. Put the data in a folder that has readonly access to an Excel user and you have a readonly 'driver'.
Another possible solution, instead you export the data for her. Why wouldn't she use OLEDB.
Cetin


>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