>In the past, I've created DSN connections and created a reference to the DSN in the "connections" section of the Project/Database. However, I have recently started using "connection strings" instead of a DSN stored on the local computer. I have figured out that the connection string info gets saved in the DBC. I have been able to locate the string info in the "Property" memo field, if I USE the DBC. However, I see that the data is compiled in some way and is not just plain text.
>
>I would like to put the connection string info in a table and have the application check for changes in the .DBF to see if anything has changed from what is stored in the "Property" memo field and, if it has, update the "propery" field. My question is this: Am I going to run into problems if I try change (udate) this compliled data programically in the DBC. Any "hints" or "gotchas" on how to do this?
>
>Thanks,
>Robert Wright
Why?
If you switched to use Connection string then keep the connection string OUT of the DB. You could use table, INI file or registry to keep your connection string (of course w/o any sensitive data as User Name and Password)
Against Stupidity the Gods themselves Contend in Vain - Johann Christoph Friedrich von Schiller
The only thing normal about database guys is their tables.