Kbase P18678: sqllogin() A pointer to the next message in the ESQL message queue.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
GOAL:
sqllogin() A pointer to the next message in the ESQL message queue.
FIX:
sqllogin() — Starts a Progress ESQL Session, is a pointer to the name of your application.
ESQL uses the first two characters of papplname to generate the first two characters of the application’s r-code filenames. If you specify a null string for this value, ESQL generates these filenames entirely as random hexadecimal number strings (plus the .r extension).
NOTE: If you preprocess with precompiling, the string that papplname specifies must
contain the same name as the application name you specify with the -a parameter
of the SQL preprocessor.
• You can pass Progress startup parameters to ESQL from the command line only using sqllogin().
• You can call sqllogin() only once from an application.
• If sqllogin() fails, the only ESQL-LIB function you can call is sqlgetmsg() to read any messages that ESQL returns.
• The sqllogin() function accepts both ESQL session (login) startup parameters and database connection parameters. However, because a database connection failure during login prevents further access to ESQL-LIB (except sqlgetmsg()), you can build a more robust application using the sqlconn() function to make all database connections, and using sqllogin() for ESQL session startup only.
• If you are running in the small client model, you cannot pass Progress session-wide client startup parameters to sqllogin(), except for the common ESQL startup parameters. For more information, see Chapter 3, “Building and Running ESQL Applications.”
• For another way to specify the application name, see the sqlapplname() function reference entry.
• For more information on r-code generation and logging in to a Progress database, see Chapter 2, “Programming with ESQL.”