Hi Paul,

It's been a while since I did this, but

A webform app can only take ?PBCommandParm= (or similar), so you need to either send that in strictly that format for it to be available in the commandline argument in the application object or write/change the aspx page to rearrange the confo?approved and pass it on

If that makes sense....

Lars

PS from doco (Deploying and running a .NET Web Forms project)

http://www.mysite.com/mypbapp/default.aspx?PBCommandParm=p1%20p2

Starting an application with command line parameters If your application requires command line parameters, you can assign values to the PBCommandParm global property before you deploy the application. For information on setting global properties, see “Global Web configuration properties”.

Application users can override the PBCommandParm parameter set at design time by adding it at the end of the application’s URL, preceded by a question mark. Multiple parameters are separated by the ASCII character code for an empty space (%20). For example, the following address, entered on a single line, uses two start-up parameters for the mypbapp Web Forms application deployed to the www.mysite.com Web site:

http://www.mysite.com/mypbapp/default.aspx?PBCommandParm=p1%20p2

If you do not include the starting page, default.aspx, in a URL that you type in a browser address bar, or if you append default.htm as the starting page, IIS still redirects you to the default.aspx page, but the browser menu and toolbar do not display. However, if you set the PBPostbackType global property to Synchronous, the redirection is made to the default_sy.aspx page that does not use AJAX update functionality.