Hi,

First, there is no way to hide the connection if you're using RV.
But, Mr. Vlad just gave me some hints on this issue a week ago. You can create all database items when program start programmtically. That is, all connection, RV, etc.. And delete it when application is closing. Of course, the .DBC should be unique in every instance.
Second approach which I'm doing is to include the DBC in EXE and encypted it. Then, you don't need to distribute the DBC to user.
But you can't modify the database propreities in run-time.

Third, using VFP 7, table opening can be specified the connection details. Please read the VFP7 doc.

:) Wilfred

Hi John,
>
>>However, why wouldn't somebody simply use a connection based on a connection >string in the DBC. This way, the connection info and RV are separated. And, >each RV can then use the connection. Since the connection has the connection >info, each RV can link to that. This would obviate the need to create a dummy >RV and share the connection from that..
>
>>Again, I might be missing something obvious here.. If I am, please point me in >the right direction..
>
>>Thanks,
>
>Even using connection string in a the DBC, if someone edit the view in the dbc,
>he still can see the password. Is there anywhere i can hide the password from being seen ?
>
>
>Thanks