|
Determining when to use a design-time connection
Note: This information is intended for UltraDev 1 users.
In many cases, UltraDev can connect to a database and obtain metadata using the same run-time connection as your Web application. In these cases, you only need to fill out the Run-Time tab. (On the Design-Time tab, the Same as Run-Time option is selected by default.)
In other cases, UltraDev cannot connect using the same run-time connection as your Web application. In these cases, you must complete the Design-Time tab so UltraDev can connect to the database and obtain the metadata it needs to populate its dialog boxes.
When is a design-time connection necessary? Start with the fact that the run-time connection is used by your Web application (not by UltraDev) on the deployment server, then ask yourself a few simple questions:
 |
What driver is used on the server? The run-time connection specifies a driver to use when the Web application is running on the server. Does the driver specified in the connection string make sense to UltraDev on your local machine? In other words, can UltraDev use an identically named driver on the local system or the actual driver on the server to talk to the database? If not, you must create a different design-time connection. |
|
For example, when defining the run-time connection for an ASP application, a Macintosh user would specify an ODBC driver or OLE-DB provider installed on the deployment server (because ASP's ADO talks only to these two interfaces). However, those drivers will probably not be installed on the Macintosh. To connect at design-time on the Macintosh, UltraDev will have to rely on a JDBC driver installed on the Macintosh (and probably on the server too). |
|
Where is the database located? If the run-time connection specifies a location in the connection string, can UltraDev use the same path to find the database? Is UltraDev even using the same database? If not, you must create a different design-time connection. |
|
For example, on the server the path to the database might be something like: |
|
C:\projects\assets\data\inventory.mdb
|
|
This path probably doesn't even exist on the system running UltraDev. Even if it does, this connection parameter would lead UltraDev down the wrong path at design-time. |
|
You can use DSNs to get around this particular problem. For more information, see Using one DSN to connect to two databases. |
|
