gpwOpen (Function)

ONLINE HELP
WINDEV, WEBDEV AND WINDEV MOBILE

Version:

Home | Sign in | English

How to use gpwOpen?
Pre-launched sessions

WINDEV

WEBDEV

WINDEV Mobile

Others

See also

gpwOpen (Function)

In french: gpwOuvre

Not available

Not available with these kinds of connection

Opens the login window or page of user groupware.

Remark: This function is required only if the User Groupware was integrated with the "Manual run" option. If the option "Automatic start" has been selected, this function is ignored.

Versions 25 and later

This function is now available for iPhone/iPad applications.

This function is now available for Android applications.

New in version 25

This function is now available for iPhone/iPad applications.

This function is now available for Android applications.

This function is now available for iPhone/iPad applications.

This function is now available for Android applications.

Example

// Opens the login window of user groupware
nRes is int = gpwOpen("c:\GpwUser")
// If the login failed
IF nRes <> gpwOk THEN
SWITCH nRes
CASE gpwCancel: Info("The Cancel button was clicked.")
CASE gpwError: Error("Error while initializing the groupware.")
CASE gpwUnknownUser: Error("Unknown user.")
CASE gpwInvalidPassword: Error("Invalid password")
END
EndProgram()
END
// Retrieve the first name of user
FirstName is string = gpwGetUserInfo(gpwInfoFirstName)
Info("Welcome" + FirstName)

Syntax

Versions 18 and later

Syntax of new User Groupware Hide the details

<Result> = gpwOpen([<Directory of groupware files>])

<Result>: Integer constant

Result regarding the opening of login window/page.
gpwCancel The user clicked the "Cancel" button found in the login window of Groupware.
gpwError An error occurred. For more details, use ErrorInfo.
gpwInvalidPassword The password is not valid. It does not correspond to the user password described in the groupware database.
gpwOk The user is connected.
gpwUnknownUser The user is not referenced in the database of user groupware.

<Directory of groupware files>: Optional character string

These data files are used to manage the users and their rights. By default, these data files are created in a subdirectory of your project (EXE\GPW_<Project name> directory).
By default, these data files are created on the server in a subdirectory of your database: directory .\GPW_<Project name>.

If this parameter corresponds to an empty string ("") or if it is not specified, the default directory of the user groupware will be used.
If this parameter corresponds to a dot ("."), the data files of user groupware will be created on the server at the root of database.

New in version 18

Syntax of new User Groupware Hide the details

<Result> = gpwOpen([<Directory of groupware files>])

<Result>: Integer constant

Result regarding the opening of login window/page.
gpwCancel The user clicked the "Cancel" button found in the login window of Groupware.
gpwError An error occurred. For more details, use ErrorInfo.
gpwInvalidPassword The password is not valid. It does not correspond to the user password described in the groupware database.
gpwOk The user is connected.
gpwUnknownUser The user is not referenced in the database of user groupware.

<Directory of groupware files>: Optional character string

These data files are used to manage the users and their rights. By default, these data files are created in a subdirectory of your project (EXE\GPW_<Project name> directory).
By default, these data files are created on the server in a subdirectory of your database: directory .\GPW_<Project name>.

If this parameter corresponds to an empty string ("") or if it is not specified, the default directory of the user groupware will be used.
If this parameter corresponds to a dot ("."), the data files of user groupware will be created on the server at the root of database.

Syntax of new User Groupware Hide the details

<Result> = gpwOpen([<Directory of groupware files>])

<Result>: Integer constant

Result regarding the opening of login window/page.
gpwCancel The user clicked the "Cancel" button found in the login window of Groupware.
gpwError An error occurred. For more details, use ErrorInfo.
gpwInvalidPassword The password is not valid. It does not correspond to the user password described in the groupware database.
gpwOk The user is connected.
gpwUnknownUser The user is not referenced in the database of user groupware.

<Directory of groupware files>: Optional character string

These data files are used to manage the users and their rights. By default, these data files are created in a subdirectory of your project (EXE\GPW_<Project name> directory).
By default, these data files are created on the server in a subdirectory of your database: directory .\GPW_<Project name>.

If this parameter corresponds to an empty string ("") or if it is not specified, the default directory of the user groupware will be used.
If this parameter corresponds to a dot ("."), the data files of user groupware will be created on the server at the root of database.

Versions 25 and later

Specific syntax for Android and iOS applications Hide the details

gpwOpen(<WLanguage procedure>)

<WLanguage procedure>: Procedure name

Name of the WLanguage procedure ("callback") called when the login window is closed.
This procedure has the following format:

PROCEDURE <Procedure name>(<Connection> is boolean)

The <Connection> is a boolean:
True if the user is connected,
False if the user is not connected.

New in version 25

Specific syntax for Android and iOS applications Hide the details

gpwOpen(<WLanguage procedure>)

<WLanguage procedure>: Procedure name

Name of the WLanguage procedure ("callback") called when the login window is closed.
This procedure has the following format:

PROCEDURE <Procedure name>(<Connection> is boolean)

The <Connection> is a boolean:
True if the user is connected,
False if the user is not connected.

Specific syntax for Android and iOS applications Hide the details

gpwOpen(<WLanguage procedure>)

<WLanguage procedure>: Procedure name

Name of the WLanguage procedure ("callback") called when the login window is closed.
This procedure has the following format:

PROCEDURE <Procedure name>(<Connection> is boolean)

The <Connection> is a boolean:
True if the user is connected,
False if the user is not connected.

Versions 25 and later

Specific syntax for Android and iOS applications Hide the details

gpwOpen(<WLanguage procedure> [, <User database>])

<WLanguage procedure>: Procedure name

Name of the WLanguage procedure ("callback") called when the login window is closed.
This procedure has the following format:

PROCEDURE <Procedure name>(<Connection> is boolean)

The <Connection> is a boolean:
True if the user is connected,
False if the user is not connected.

<User database>: Integer constant

Database of users and rights to use:
gpwDatabaseDefault The database of users and rights depends on the application start mode:
if the application is launched in GO mode (Go simulator or Go on phone with WMDev), the test database will be used as the database of users and rights.
if the application is launched from the version deployed on the mobile device, or an Android emulator, the production database will be used as the database of users and rights.
gpwDatabaseProduction Forces the use of the user and production rights database regardless of the application start mode.
gpwDatabaseTest Forces the use of the user and test rights database regardless of the application start mode.

New in version 25

Specific syntax for Android and iOS applications Hide the details

gpwOpen(<WLanguage procedure> [, <User database>])

<WLanguage procedure>: Procedure name

Name of the WLanguage procedure ("callback") called when the login window is closed.
This procedure has the following format:

PROCEDURE <Procedure name>(<Connection> is boolean)

The <Connection> is a boolean:
True if the user is connected,
False if the user is not connected.

<User database>: Integer constant

Database of users and rights to use:
gpwDatabaseDefault The database of users and rights depends on the application start mode:
if the application is launched in GO mode (Go simulator or Go on phone with WMDev), the test database will be used as the database of users and rights.
if the application is launched from the version deployed on the mobile device, or an Android emulator, the production database will be used as the database of users and rights.
gpwDatabaseProduction Forces the use of the user and production rights database regardless of the application start mode.
gpwDatabaseTest Forces the use of the user and test rights database regardless of the application start mode.

Specific syntax for Android and iOS applications Hide the details

gpwOpen(<WLanguage procedure> [, <User database>])

<WLanguage procedure>: Procedure name

Name of the WLanguage procedure ("callback") called when the login window is closed.
This procedure has the following format:

PROCEDURE <Procedure name>(<Connection> is boolean)

The <Connection> is a boolean:
True if the user is connected,
False if the user is not connected.

<User database>: Integer constant

Database of users and rights to use:
gpwDatabaseDefault The database of users and rights depends on the application start mode:
if the application is launched in GO mode (Go simulator or Go on phone with WMDev), the test database will be used as the database of users and rights.
if the application is launched from the version deployed on the mobile device, or an Android emulator, the production database will be used as the database of users and rights.
gpwDatabaseProduction Forces the use of the user and production rights database regardless of the application start mode.
gpwDatabaseTest Forces the use of the user and test rights database regardless of the application start mode.

Syntax of the former User Groupware (kept for backward compatibility) Hide the details

<Result> = gpwOpen([<Directory of rights file> [, <User files directory>]])

<Result>: Integer constant

Result regarding the opening of login window/page.
gpwCancel The user clicked the "Cancel" button found in the login window of Groupware.
gpwError An error occurred. For more details, use ErrorInfo.
gpwInvalidPassword The password is not valid. It does not correspond to the user password described in the groupware database.
gpwOk The user is connected.
gpwUnknownUser The user is not referenced in the database of user groupware.

<Directory of rights file>: Optional character string

These data files are used to manage the rights granted to the users for the different windows of the application. These files are specific to the application. By default, these data files are created in a subdirectory of your project (EXE\GPW_<Project name> directory).
By default, these data files are created on the server in a subdirectory of your database: directory .\GPW_<Project name>.

If this parameter corresponds to an empty string ("") or if it is not specified, the default directory of the user groupware will be used.
If this parameter corresponds to a dot ("."), the data files of user groupware will be created on the server at the root of database.

<User files directory>: Optional character string

These data files can be common to several applications. By default, these data files are created in a subdirectory of your project (EXE\GPW_<Project name> directory). You can define the location of the User Groupware files common to several applications. In this case, you must specify the path of data files to use.
By default, these data files are created on the server in a subdirectory of your database: directory .\GPW_<Project name>.

If this parameter corresponds to an empty string ("") or if it is not specified, the default directory of the user groupware will be used.
If this parameter corresponds to a dot ("."), the data files of user groupware will be created on the server at the root of database.

Remarks

How to use gpwOpen?

gpwOpen allows you to define the User Groupware startup mode. This allows you to perform other actions before opening the User Groupware login window or page: execute code, open windows or pages, etc.

Usage example of this function: in a multilingual application that is using the User Groupware, the first window or page of the application is used to choose the runtime language. When creating the application, you must:

choose not to automatically run the User Groupware during its integration
open the window or page for language selection as first application window, then call the login window or page with gpwOpen.

Versions 25 and later

If the User Groupware is enabled in "Manual run" mode, the following operations must performed:

Do not define a first project window.
Call gpwOpen in the "Initializing" event of the project.
Open the first project window from the WLanguage code of the procedure passed as a parameter to gpwOpen.

New in version 25

If the User Groupware is enabled in "Manual run" mode, the following operations must performed:

Do not define a first project window.
Call gpwOpen in the "Initializing" event of the project.
Open the first project window from the WLanguage code of the procedure passed as a parameter to gpwOpen.

If the User Groupware is enabled in "Manual run" mode, the following operations must performed:

Do not define a first project window.
Call gpwOpen in the "Initializing" event of the project.
Open the first project window from the WLanguage code of the procedure passed as a parameter to gpwOpen.

Versions 20 and later

Pre-launched sessions

If your project uses pre-launched sessions, this function must not be used in the project initialization event. This function must be used in the "Initializing the project after connection to the site" event.

New in version 20

Pre-launched sessions

Business / UI classification: Neutral code

Component: wd270gpu.dll