The way we do it (and I'm sure there are several different ways) is with a one record table that stores the connection info. This dbf sits in the directory with the app and the fields are filled in via our install. We also provide a small app to edit it if necessary.
>My VFP 6.0 app reads SQL tables from an accounting package written by another vendor. On my development machine, it is very easy to establish the ODBC connection because I know the name of my server and the database I want to access. However, when I distribute my EXE, the user will have to specify the name of their own server and database. I'm looking for the most user-friendly solution to establish the user's connection. Should I include VFP's connection designer in the EXE or has anyone already written a better user interface to specify connection properties?
"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
