Tommy Pruitt wrote:
Using a MySQL server with an ODBC connection. I have created a database/forms/queries/reports on my pc and then copied that database to several users around the office. When using the forms and entering data from my pc all is well. If I go to another pc and fill in the form not all of the fields are submitted/saved to the SQL server. We are all using the same username/password to access the server and have the same version of ODBC connector.
Turn on logging in your ODBC driver configuration and point us to where we can look at it. We don't need all of the log (or we'll be here all day trying to wading through useless junk.
I also assume you know that mysql connections are session dependent which means that others don't get to see the updates until that user has terminated his session. This is not generally a problem with direct mysql interaction because the server frees up the session connection information rapidly, i.e. the data gets written almost immediately to the server, but can be a problem within OOo (I have had this problem before at work) where some form of locking seems to take place. I must admit to not having traced the SQL calls when this happens so I don't really know what's going on behind the scenes. You might try turning off the "connection pooling" option within the menu Tools>Database configuration panel to see if that makes a difference.
Why use a single user / pwd combo instead of individual ones for each user ? I assume that your mysql server configuration takes account of the fact that the universal user / pwd connection combo should be machine or host independent, i.e. not dependent on a specific host name or IP address ?
Alex Alex --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
