#### USER# command

Specifies user IDs for logging on to SQL or ODBC databases used by the report.

    USER#=<userids>
    «<userids> is a string.»

For example:

`user0=SmithJ`

If the report accesses more than one password-protected database, multiple user IDs can be passed by incrementing the USER index number. For example:

`user0=SmithJ&user1=JohnS&user2=JSmith`

USER# is normally used in conjunction with the PASSWORD# command. For example:

`user0=SmithJ&password0=secret&user1=JohnS&password1=mystery`

If the report contains subreports that require user IDs for logging on to SQL or ODBC data sources, use the following syntax in the URL:

`user#@subreportname`

For example:

`user0@Crosstab=jimmys&password0@Crosstab=jimmyz`

Note: If an existing report is inserted as the subreport, then the subreport name includes the file extension (for example, user0@subreportname.rpt). However, if the subreport was created inside the main report (with Insert Subreport and using the Report Expert to create the new report) then the name of the subreport usually does not contain a file extension (for example, user0@subreportname) unless one is added in the "Report Name" text box of the Insert Subreport dialog box.

Note: Make sure user IDs appear in the URL in the same order in which the password-protected databases appear in the report. Additionally, subreport user IDs must appear in the same order that the subreports appear in the report. If user IDs are not passed using the URL address, the user is prompted for logon information at runtime.

Note: Reports are not be shared if there are logon requirements.

Seagate Software, Inc. http://www.seagatesoftware.com Please send comments to: techpubs@seagatesoftware.com