|
Using one DSN to connect to two databases
If you use a test database to develop your application, you can use a single DSN to connect to both the test database and the deployment database—and thus avoid creating a different design-time connection to the test database. For this technique to work, you must be able to define DSNs in two places:
 |
On the server hosting the deployment database |
|
On the local or network-accessible system hosting the test database |
First, define a DSN on the server hosting the deployment database and specify the path to the deployment database. Second, define a DSN on the local or network-accessible system hosting the test database, give it the same name as the server DSN, and specify the path to the test database (not the deployment database). Finally, use the single DSN name in the Run-Time tab in the Define Connection dialog box.
By defining two DSNs with the same name but different paths, you can trick UltraDev down the right path to the database. When the deployment server looks up the DSN on the host system, it will find the path to the deployment database. When UltraDev looks up the same DSN on the host system, however, it will find the different path to the test database.
|
