I always forget about that. But does it really happen on the fly, or does VFP drop the connection, change the DB, and then reconnect? That could be a bit of a performance hit. You're absolutely right about the stored procedure. In fact, it's probably the best solution (IMHO) speed wise.
>DBSETPROP() can be used to change connection.database property on fly, so it's possible to reach different databases using the same DSN. Also, it's possible (i guess) to call back-end stored procedure which will access diferent databases.
"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
