Norma, what you can do is:

1. Set your views to "share connection"
2. When you launch your app, connect to the server using SQLSTRINGCONNECT() and do not close this connection until you close the app.
3. All your views will reuse this connection (because the ShareConnection)

You can bury the connection settings in the code and probably read this settings from an INI file or somewhere else.

Also, do not delete the connection defined in your DBC, just store some dummy information in the login name/pwd that you have on your DBC.


>Hi all, I am concerned about the security issues with the database server and the application server. I have been working with a connection inside the dbc for the remotes view with a fixed user/pwd, but i will like to use the user/pwd of the rdms in order to protect the data, (some users can only select etc) So if i leave the connection witout user/pwd the login prompt of the odbc appearch each time the view is 'used' , change form etc.close form etc. What would be the approach to use the login data of the application in order to pass it seamlessly to the DBserver so that the security issues of grants, selects, inserts etc be validated. I know I can prevent data modification from MY app via code and some framework's security features, but what if someone goes to the dbc and modifies via vfp ?
>
>Thanks
>
>Norman Avila