Okay - it's working, but only when run locally - on my mobile phone I get the following issue (screenshot no.1)

connection:CacheName='quarry'

Connection cache name cannot be null.

The user selects the industry type, then I put that into a global string to do a choose case to determine database connection parameters (see below).

choose case gs_industry
			
	case "Quarry"
		sqlca.DBMS			= "ODB-ASA"
		sqlca.userid			= "dba"
		sqlca.dbpass		= "sql"
		sqlca.database		= "jpe"
		sqlca.dbparm		= "CacheName='quarry' ConnectString='DSN=jpe;UID=dba;PWD=sql'"
		
	case "Waste"
		sqlca.DBMS			= "ODB-ASA"
		sqlca.userid			= "dba"
		sqlca.dbpass		= "sql"
		sqlca.database		= "regen"
		sqlca.dbparm		= "CacheName='waste' ConnectString='DSN=regen;UID=dba;PWD=sql'"
			
			
	case else 
		return
		
end choose

I then have in my AEM the two data objects (see screenshot 2)

You'll also see I have my sql anywhere 16 data sources tested and working fine (see screenshot 3)

After I choose my case, I then do a CONNECT USING sqlca; and select the username from the database.

CONNECT using sqlca;
IF sqlca.sqlcode = 0 THEN
	SELECT string1 INTO :ls_name FROM base WHERE file = -21 AND code = :ls_code USING sqlca;
	st_name.text = ls_name
ELSE
	MessageBox("ERROR:database connection:" + sqlca.dbparm, sqlca.sqlerrtext)
END IF
DISCONNECT using sqlca;

This is now working when I run locally, I know I am able to collect a unique username in each database depending on which industry I choose.

Marc -

   You could also host the names of the four databases in an INI file, as was mentioned above. The INI file is deployed with your application and is accessed as the logon window is being built. There are now three fields in the LOGON window, the bottom one being a dddw that displays the available databases.

   This option is FAR easier to code and maintain, and since hte users still need to know their credentials for each database, the security is not really an issue.


Good Luck,

Olan

for my client server app i store the server/database connection information in an ini file (for easy copy between workstations).  each database server has a name that allows the user to easily know what it is.  This info can be saved in the registry or yet another database if you prefer.

anyway, the user selects the database they want to connect to in the login screen, along with username/password, the system looks up the connection information (server, database, port, driver, etc).  So, the databases can be on different servers and can even be different (sql server vs oracle vs sql anywhere vs ase vs postgresql) etc.

The only reason you need a database connection for compile is the syntax check.

Many in your situation will have a 'credentials' database that only has a few tables that identify users. This would include the name of the database that the application will work from.

The login window would connect to the credentials database to find out what application database to use. It would then disconnect from credentials and connect to application.