I think then you'll have to use the "database..table" solution I mentioned. The connection is to the server, not the database. Setting the database in the ODBC connection is just a convenience.
I don't know how experienced you are with SQL Server, but stored procedures are perfect for this kind of thing, especially for inserts and updates. That way you wouldn't have to worry about changing the database on the front end. All you have to do is send the values to the stored procedure and let it handle the work. Check it out!
>I want to try DBSetProp, but my problem is that I make the connection with SQLCONNECT not with a connection in a .DBC so I don't have a name for my connection. And I don't saw the same command with SQLSetProp. So is it possible to do it with a connection create by SqlConnect ?
"It is an important and popular fact that things are not always what they seem. For instance, on the planet Earth, man had always assumed that he was more intelligent than dolphins because he had achieved so much -- the wheel, New York, wars and so on -- whilst all the dolphins had ever done was muck about in the water having a good time. But conversely, the dolphins had always believed that they were far more intelligent than man -- for precisely the same reasons." - Douglas Adams
